ISAC Rel-19

RAN1#116

9.7 Study on channel modelling for Integrated Sensing And Communication (ISAC) for NR

Please refer to RP-234069 for detailed scope of the SI.

R1-2401768 Session notes for 9.7 (Study on channel modelling for Integrated Sensing And Communication for NR) Ad-Hoc Chair (Huawei)

Friday decision: The session notes are endorsed and contents reflected below.

[116-R19-ISAC] – Yingyang (xiaomi)

Email discussion on Rel-19 ISAC channel model

- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2400574 Proposed work plan on channel modelling for ISAC xiaomi, AT&T

R1-2400575 Discussion on CR to introduce channel model for ISAC xiaomi, AT&T

9.7.1 ISAC deployment scenarios

R1-2401346 Deployment scenarios for ISAC Continental Automotive

· Decisions and agreements made by RAN1 in this SI (FS_ISAC_NR) should be based on and consistent with the assumption that the ISAC SI targets “sensing as a service” as priority.

· For the different sensing targets, consider the prioritization in terms of deployment types and sensing modes shown in Table 1.

· For the work to be done in the ISAC SI (FS_ISAC_NR), consider the work segmentation/division illustrated in Figure 1.

· Automotive-relevant ISAC services include, at least, the scenarios indicated in Table 2. These involve both outdoor and indoor situations, in- and out-of-coverage, and potentially supported by Uu- and/or PC5-based sensing.

Decision: The document is noted.

R1-2400529 Discussion on ISAC Deployment Scenarios Ericsson

· To model sensing objects, study parameters of their locations, trajectories, radar cross-sections, and clutter types.

· RAN1 to define new sensing scenarios and ensure that the sensing-related model additions to TR 38.901, when enabled, do not have an undue effect on perceived communication quality and potential conclusions thereof.

· For TRP-UE bistatic and UE-TRP bistatic sensing modes, the direct propagation path between sensing transmitter and sensing receiver can be referred to the existing gNB-UE communication channel model.

· For TRP-TRP bistatic, TRP monostatic, UE monostatic, and UE-UE bistatic sensing modes, the direct propagation path between sensing transmitter and sensing receiver is not defined in TR 38.901 and needs to be studied.

· A sensing scenario models only one type of sensing target, either indoor or outdoor.

· Support the following scenarios:

o All of the sensing transmitters, sensing receivers, and targets are outdoor.

o All of the sensing transmitters, sensing receivers, and targets are indoor.

o If outdoor gNBs are the sensing transmitters/receivers, the targets are indoor.

· Both indoor and outdoor UAVs as sensing target are in the scope of Rel-19 ISAC channel modelling SI.

· The pairing between sensing scenario and existing deployment scenarios in TR 38.901, is defined according to Table 1.

Decision: The document is noted.

R1-2400068 Discussion on ISAC deployment scenarios Spreadtrum Communications

R1-2400126 Deployment scenarios for ISAC channel model Huawei, HiSilicon

R1-2400155 Discussion for ISAC deployment scenarios New H3C Technologies Co., Ltd.

R1-2401468 Overview of ISAC Deployment Scenarios Tiami Networks (rev of R1-2400167)

R1-2400174 Measurement data for ISAC deployment scenarios NIST

R1-2400175 Power Calibration for Radar Cross Section (RCS) Measurement NIST

R1-2400256 Views on Rel-19 ISAC deployment scenarios vivo

R1-2400341 Discussion on ISAC deployment scenarios CMCC

R1-2400447 Discussion on ISAC deployment scenarios CATT

R1-2400504 Deployment scenarios for ISAC channel modeling Intel Corporation

R1-2400572 Deployment scenarios and evaluation assumptions for ISAC channel model xiaomi

R1-2400616 Discussion on ISAC deployment scenarios OPPO

R1-2400644 ISAC Deployment Scenarios Sharp

R1-2400648 Discussion on ISAC deployment scenarios Nokia, Nokia Shanghai Bell

R1-2400652 Proposals for Integrated Sensing And Communication (ISAC) Deployment Scenarios NTPU

R1-2400673 Discussion on ISAC deployment scenarios China Telecom

R1-2400690 Deployment scenarios for integrated sensing and communication with NR NVIDIA

R1-2400746 Discussion on ISAC deployment scenarios Samsung

R1-2400759 Discussion on deployment scenarios for Integrated Sensing and Communication CICTCI

R1-2400791 Discussion on ISAC deployment scenarios LG Electronics

R1-2400801 Discussion on ISAC Deployment Scenarios Lekha Wireless Solutions

R1-2400866 Considerations on ISAC Deployment Scenario Sony

R1-2400881 Discussion on ISAC deployment scenarios and requirements EURECOM

R1-2400898 Considerations on ISCA deployment scenarios CAICT

R1-2400931 Discussion on ISAC deployment scenarios TOYOTA InfoTechnology Center

R1-2400935 Discussions on ISAC deployment scenarios Ruijie Network Co. Ltd

R1-2400960 ISAC Deployment Scenarios Panasonic

R1-2401026 Discussion on ISAC deployment scenarios Apple

R1-2401040 Discussion on ISAC deployment scenarios InterDigital, Inc.

R1-2401063 Discussion on ISAC deployment scenarios ZTE Corporation

R1-2401178 Discussion on ISAC deployment scenarios ITL

R1-2401220 Discussion on ISAC deployment scenarios Lenovo

R1-2401340 Discussions on ISAC deployment scenarios IIT Kanpur

R1-2401355 Views on Deployment Scenarios for ISAC for NR AT&T, FirstNet

R1-2401455 Discussion on ISAC deployment scenarios Qualcomm Incorporated

R1-2401466 Discussion on ISAC deployment scenario MediaTek

R1-2400953 FL summary on ISAC deployment scenarios Moderator (AT&T)

Presented in Tuesday session.

R1-2401705 FL summary#2 on ISAC deployment scenarios Moderator (AT&T)

From Thursday session

Agreement

For progressing ISAC study, the following sensing targets and existing communication scenarios will be considered as a starting point:

· Note1: the table below does not imply that the sensing target will be placed at positions defined for UEs and BSs in the scenarios in the right column.

· Note2: the table below does not imply that UEs are necessarily placed at positions defined for UEs in the scenarios in the right column.

· Note3: the existing communication scenarios are listed with the intent to use the evaluation parameters defined for those scenarios, as a starting point.

Sensing Targets	scenarios
UAVs	RMa-AV, UMa-AV, UMi-AV (TR 36.777)
Humans indoors	InF, Indoor Office, [Indoor Room (TR 38.808)], [UMi, UMa]
Humans outdoors	UMi, UMa, [RMa]
Automotive vehicles (at least outdoors)	Highway, Urban grid, UMa, UMi, RMa
Automated guided vehicles (e.g. in indoor factories)	InF
Objects creating hazards on roads/railways (examples defined in TR 22.837)	Highway, Urban grid, HST

Agreement

For ISAC channel modelling, RAN1 uses the sensing related terminology as defined in TS22.137 or TR22.837 as a starting point for discussion purposes with the following definitions:

· Sensing transmitter: the TRP or a UE that sends out the sensing signal which the sensing service will use in its operation. A sensing transmitter can be located in the same or different TRP or a UE as the sensing receiver.

· Sensing receiver: the TRP or a UE that receives the sensing signal which the sensing service will use in its operation. A sensing receiver can be located in the same or different TRP or a UE as the sensing transmitter.

· Sensing target: target that need to be sensed by deriving characteristics of the objects within the environment from the sensing signal.

· Background environment: background (clutter and/or environmental objects) that are not the sensing target(s).

· Mono-static sensing: sensing where the sensing transmitter and sensing receiver are co-located in the same TRP or UE.

· Bi-static sensing: sensing where the sensing transmitter and sensing receiver are in different TRPs or UEs.

· Multi-static sensing: sensing where there are multiple sensing transmitters and/or multiple sensing receivers, for a sensing target.

· Sensing signal: Transmissions on the 3GPP radio interface that can be used for sensing purposes.

9.7.22 ISAC channel modelling

R1-2400810 Options for ISAC Channel Modelling Keysight Technologies UK Ltd

· Choose the channel modelling framework for each use case among the deterministic, geometry based stochastic, hybrid of deterministic and stochastic, or interpolation-based hybrid approach.

· Identify and specify required model extensions for the selected channel modelling frameworks for each use case.

Decision: The document is noted.

R1-2400257 Views on Rel-19 ISAC channel modeling vivo

· RAN1 studies a common channel model formed by two components: one for sensing target(s) and the other for background, both containing a set of common parameters.

· RAN1 defines the specific value for each common parameter in the experiment campaign, associated to either a deployment scenario, or a use case, or a sensing mode, or these combinations.

· RAN1 studies a sensing channel model, identifying whether a joint channel model for sensing and communication is necessary.

· RAN1 study focuses on the stochastic channel modeling, and optionally takes into account the RT-based mechanism to generate sensing channel parameters.

· RAN1 works on both SLS-based and LLS-based channel models in Rel-19.

· RAN1 works on the channel modeling in FR1, FR2, and FR3 (i.e., 7-24GHz band).

· RAN1 studies on a common channel model, in consideration of the work plan with Part-1, Par-2, and Part-3, as a starting point.

· As a study of sensing channel model in Rel-19, RAN1 prioritizes the bistatic sensing mode (TRP-UE, UE-TRP) and TRP monostatic sensing mode.

· RAN1 studies the legacy method in TR 38.901 to determine the LOS/NLOS state for the sensing link.

· RAN1 prioritizes the common pathloss equation for both bi-static and mono-static sensing mode.

· RAN1 studies whether a calibrate pathloss for sensing channel modeling is needed or not.

· RAN1 studies a sensing channel formed by both sensing target channel component and environment channel component, i.e., , as a starting point.

· RAN1 prioritizes the method that the background clusters generation is correlated with communication channel.

· Studying the new propagation model should avoid the changes of statistic characteristics and behaviors associated with the communication channel.

· Study unified Doppler formula for both communication channel and sensing channel.

· Study micro-Doppler to capture micromotion of human body in addition to macro-Doppler.

· Study the enhanced spatial consistency for sensing channel; the spatial consistency modeling defined in TR38.901 can be a starting point, in consideration of sensing-target-specific network topology.

· Study the RCS model, at least in consideration of frequency, physical geometry and electromagnetic properties of the target, the direction of signal path.

· Study the RCS model for both bistatic sensing and mono-static sensing.

· Study the RCS model focusing on sensing targets other than environment targets.

· Study the RCS modeling in consideration of the sensing requirements for different scenarios or use cases.

· Study the RCS modeling by small-scale level model and/or large-scale level model.

· Study the RCS modeling with single-point value and/or multi-point values.

· RAN1 considers the experiment only based methodology and the ray tracing combination-based methodology for common channel model design.

· RAN1 starts the experiment campaign to validate a common channel model with the relevant parameters (as an example in the Annex-3).

· The discussion on the skeleton of TR can be started in the beginning of the meeting, and it should be completed within the first two meetings.

· The CR submission related to the modification and extension on TR38.901 can be started from RAN1#119 in Q4 in order to ensure the work efficiency.

· All the contents of TR can be divided into two parts; one will be captured in the main section, and the other will be captured in an annex or an additional file.

· RAN1 calibrates the newly defined channel model in consideration of the performance consistency between sensing and communication links.

Decision: The document is noted.

R1-2400069 Discussion on ISAC channel modeling Spreadtrum Communications

R1-2400127 Channel modeling methodology for ISAC Huawei, HiSilicon

R1-2400168 ISAC Channel Modeling Considerations Tiami Networks

R1-2400173 ISAC channel measurements and results for shared clusters BUPT, CMCC

R1-2400342 Discussion on channel modeling methodolgy for ISAC CMCC, BUPT, SEU, PML

R1-2400448 Discussion on ISAC channel modelling CATT

R1-2400505 Discussion on ISAC channel modeling Intel Corporation

R1-2400530 Discussion on ISAC Channel Modelling Ericsson

R1-2400573 Discussion on ISAC channel model xiaomi, BUPT

R1-2400617 Study on ISAC channel modelling OPPO

R1-2400645 ISAC Channel modelling Sharp

R1-2400649 Discussion on ISAC channel modelling Nokia, Nokia Shanghai Bell

R1-2400691 Channel modeling for integrated sensing and communication with NR NVIDIA

R1-2400747 Discussion on ISAC channel modelling Samsung

R1-2400760 Discussion on channel modelling for Integrated Sensing and Communication CICTCI

R1-2400792 Discussion on ISAC channel modelling LG Electronics

R1-2400818 Discussion on Channel Modelling for ISAC Lenovo

R1-2400841 Discussion on channel modelling for Integrated Sensing and Communication (ISAC) Southeast University

R1-2400867 Considerations on ISAC Channel Model Sony

R1-2400882 Discussion on ISAC channel modeling EURECOM

R1-2400899 Considerations on ISAC channel modelling CAICT

R1-2400932 Discussion on ISAC channel modelling TOYOTA InfoTechnology Center

R1-2400961 ISAC Channel Modelling Panasonic

R1-2401027 Discussion on ISAC channel modelling Apple

R1-2401041 Discussion on ISAC channel modeling InterDigital, Inc.

R1-2401064 Discussion on channel modelling for ISAC ZTE Corporation, BJTU

R1-2401347 Channel modelling for ISAC Continental Automotive

R1-2401356 Views on ISAC Channel Modelling AT&T

R1-2401456 Discussion on ISAC channel modelling Qualcomm Incorporated

R1-2401467 Discussion on ISAC channel modelling MediaTek

R1-2401494 Summary #1 on ISAC channel modeling Moderator (xiaomi)

Presented in Tuesday session.

R1-2401495 Summary #2 on ISAC channel modeling Moderator (xiaomi)

From Thursday session

Agreement

The common framework for ISAC channel model is composed of a component of target channel and a component of background channel,

Target channel includes all [multipath] components impacted by the sensing target(s).

FFS details of the target channel

Background channel includes other [multipath] components not belonging to target channel

FFS details of the background channel

FFS whether/how to model environment object(s), i.e., object(s) with known location, other than sensing target(s)

FFS whether/how to model propagation path(s) between the target(s) and the environment object(s)

FFS whether/how to model propagation path(s) between the target(s) and the stochastic clutter(s)
Note: the notation H_ISAC can be revised later if needed

Final summary in R1-2401496.

RAN1#116-bis

9.7 Study on channel modelling for Integrated Sensing And Communication (ISAC) for NR

Please refer to RP-240799 for detailed scope of the SI.

R1-2403664 Session notes for 9.7 (Study on channel modelling for Integrated Sensing And Communication for NR) Ad-Hoc Chair (Huawei)

Friday decision: The session notes are endorsed and contents reflected below.

[116bis-R19-ISAC] – Yingyang (xiaomi)

Email discussion on Rel-19 ISAC channel model

- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

9.7.1 ISAC deployment scenarios

R1-2401997 Deployment scenarios for ISAC channel model Huawei, HiSilicon

R1-2402117 Discussion on ISAC deployment scenarios Spreadtrum Communications

R1-2402131 Deployment scenarios for ISAC channel modeling Intel Corporation

R1-2402177 Discussion on ISAC deployment scenarios and requirements EURECOM

R1-2402254 Views on Rel-19 ISAC deployment scenarios vivo

R1-2402289 Discussion on ISAC Deployment Scenarios Nanjing Ericsson Panda Com Ltd

R1-2402340 Discussion on ISAC deployment scenarios OPPO

R1-2402395 Discussion on ISAC deployment scenarios CATT, CICTCI

R1-2402478 Discussion on ISAC deployment scenarios Samsung

R1-2402522 Discussion on ISAC deployment scenarios China Telecom

R1-2402577 Discussion on ISAC deployment scenarios CMCC, China Southern Power Grid

R1-2402599 Discussion on ISAC deployment scenarios Nokia, Nokia Shanghai Bell

R1-2402607 Overview of ISAC Deployment scenarios Tiami Networks

R1-2402678 Deployment scenarios and evaluation assumptions for ISAC channel Xiaomi

R1-2402703 Discussion on ISAC deployment scenarios ZTE Corporation

R1-2402815 Discussion on ISAC deployment scenarios LG Electronics

R1-2402851 Deployment scenarios for integrated sensing and communication with NR NVIDIA

R1-2402896 Discussion on ISAC deployment scenarios Apple

R1-2402914 Discussion on ISAC deployment scenarios InterDigital, Inc.

R1-2402940 Discussion on ISAC deployment scenario MediaTek

R1-2402979 Discussion on ISAC Deployment Scenarios Sony

R1-2403070 Discussions on ISAC deployment scenarios Ruijie Networks Co. Ltd

R1-2403087 Discussion on ISAC deployment scenarios Lenovo

R1-2403133 Discussion on ISAC Deployment Scenarios Panasonic

R1-2403142 Deployment Scenarios for ISAC Channel Modeling AT&T, FirstNet

R1-2403159 Considerations on ISCA deployment scenarios CAICT

R1-2403206 Discussion on ISAC deployment scenarios Qualcomm Incorporated

R1-2403256 Study on deployment scenarios for ISAC channel modelling NTT DOCOMO, INC.

R1-2403386 Discussion on ISAC Deployment Scenarios IIT Kanpur, Indian Institute of Technology Madras

R1-2403048 FL Summary #1 on ISAC Deployment Scenarios Moderator (AT&T)

From Tuesday session

Agreement

RAN1 agrees the following ISAC terminology with minor modifications as follows:

For ISAC channel modelling, RAN1 uses the sensing related terminology as defined in TS22.137 or TR22.837 as a starting point for discussion purposes with the following definitions:

1. Sensing transmitter: the TRP or a UE that sends out the sensing signal which the sensing service will use in its operation. A sensing transmitter can be located in the same or different TRP or a UE as the sensing receiver.

2. Sensing receiver: the TRP or a UE that receives the sensing signal which the sensing service will use in its operation. A sensing receiver can be located in the same or different TRP or a UE as the sensing transmitter.

3. Sensing target: target that need to be sensed by deriving characteristics of the objects within the environment from the sensing signal.

4. Background environment: background (clutter and/or environmental objects) that are not the sensing target(s).

5. Mono-static sensing: sensing where ~~the~~ a sensing transmitter that transmits a sensing signal and a sensing receiver that receives the sensing signal are co-located in the same TRP or UE.

6. Bi-static sensing: sensing where ~~the~~ a sensing transmitter that transmits a sensing signal and a sensing receiver that receives the sensing signal are not co-located in the same TRP or UE~~in different TRPs or UEs~~.

7. Multi-static sensing: sensing where there are multiple sensing transmitters and/or multiple sensing receivers, for a sensing target.

8. Sensing signal: Transmissions on the 3GPP radio interface that can be used for sensing purposes.

R1-2403049 FL Summary #2 on ISAC Deployment Scenarios Moderator (AT&T)

Presented in Wednesday session

R1-2403050 FL Summary #3 on ISAC Deployment Scenarios Moderator (AT&T)

From Thursday session

Agreement

Any TRP and/or UE location in the corresponding communication scenario can be selected as sensing transmitters and receivers locations. FFS: other possible sensing transmitters and receivers locations.

Agreement

The following table can be used by companies to propose values for each sensing target.

· Additional parameters/rows can be added if needed

Table x. Evaluation parameter template for sensing scenarios

Parameters		Value
Applicable communication scenarios
Sensing transmitters and receivers properties
Supported sensing modes
Sensing target	Outdoor/indoor
	3D mobility
	3D distribution
	Orientation
	Physical characteristics (e.g., size)
[Unintended/Environment objects]	Types
	3D mobility
	3D distribution
	Orientation
	Physical characteristics (e.g., size)
[Sensing area]
Minimum 3D distances between pairs of Tx/Rx/sensing target/[unintended objects]

9.7.22 ISAC channel modelling

R1-2401998 Channel modeling methodology for ISAC Huawei, HiSilicon

R1-2402118 Discussion on ISAC channel modeling Spreadtrum Communications

R1-2402132 Discussion on ISAC channel modeling Intel Corporation

R1-2402178 Discussion on ISAC channel modeling EURECOM

R1-2402255 Views on Rel-19 ISAC channel modelling vivo

R1-2402290 Discussion on ISAC Channel Modelling Nanjing Ericsson Panda Com Ltd

R1-2402341 Study on ISAC channel modelling OPPO

R1-2402396 Discussion on ISAC channel modelling CATT, CICTCI

R1-2402408 Discussion on ISAC channel modelling SHARP

R1-2402479 Discussion on ISAC channel modelling Samsung

R1-2402523 Discussion on ISAC channel modelling China Telecom

R1-2402578 Discussion on channel modeling methodology for ISAC CMCC, BUPT, SEU, PML

R1-2402600 Discussion on ISAC channel modelling Nokia, Nokia Shanghai Bell

R1-2402608 ISAC Channel Modeling Considerations Tiami Networks

R1-2402679 Discussion on ISAC channel model Xiaomi, BUPT

R1-2402704 Discussion on channel modelling for ISAC ZTE Corporation, BJTU

R1-2402708 Discussion on ISAC channel modeling BUPT, CMCC

R1-2402816 Discussion on ISAC channel modelling LG Electronics

R1-2402852 Channel modeling for integrated sensing and communication with NR NVIDIA

R1-2402897 Discussion on ISAC channel modelling Apple

R1-2402915 Discussion on ISAC channel modeling InterDigital, Inc.

R1-2402941 Discussion on ISAC channel modelling MediaTek

R1-2402980 Discussion on ISAC Channel Model Sony

R1-2403078 Discussion on Channel Modelling for ISAC Lenovo

R1-2403107 Information on ISAC channel modeling Nokia, NIST, Anritsu, Keysight, AT&T, Ericsson, Sharp, NYU Wireless, Motorola Mobility, Futurewei

R1-2403135 Discussion ISAC channel modelling Panasonic

R1-2403143 Discussions on ISAC Channel Modeling AT&T

R1-2403160 Considerations on ISAC channel modelling CAICT

R1-2403207 Discussion on ISAC channel modelling Qualcomm Incorporated

R1-2403262 Discussion on channel modeling for Integrated Sensing and Communication (ISAC) Southeast University

R1-2403372 Discussions on ISAC Channel Modelling ITL (Late submission)

R1-2403382 Discussion on ISAC channel modeling in automotive DENSO CORPORATION

R1-2402680 Summary #1 on ISAC channel modelling Moderator (Xiaomi)

Presented in Tuesday session.

R1-2402681 Summary #2 on ISAC channel modelling Moderator (Xiaomi)

From Wednesday session

Agreement

The following cases of radio propagation in the target channel are considered for the study

Case	Tx-target	Target-Rx
1	LOS condition	LOS condition
2	LOS condition	NLOS condition
3	NLOS condition	LOS condition
4	NLOS condition	NLOS condition

· Case 1/2/3/4 can be considered for bistatic sensing mode

· At least Case 1/4 can be considered for monostatic sensing mode

· Note: It doesn’t imply the channel response for each link is separately generated then concatenated

· FFS how to determine LOS condition and NLOS condition, e.g., based on LOS probability, or determined based on geometrical locations of environment object (EO).

· In LOS condition, line of sight ray(s) are present between Tx/Rx and target, and there may or may not exist non-line of sight ray(s) between Tx/Rx and target too

· In NLOS condition, there only exist non-line of sight ray(s) between Tx/Rx and target.

Agreement

· In the target channel between Tx and Rx, scattering of a sensing target can be modelled as single scattering point or multiple scattering points

· FFS one or multiple incoming/output rays corresponding to a scattering point

· FFS how to select single or multiple scattering points for the target, e.g. depending on the distance between target and Tx/Rx, size/shape of target, etc.

· Note: the sensing target can be assumed in far field of sensing Tx/Rx.

· FFS details to model the single or multiple scattering points.

Agreement

RCS of a physical object shows dependency to at least the following factors:

Type of the object

The size of the object
The material of the object
The shape of the object

Orientation of the object
FFS: Distance between Tx/Rx and the object
The incident angle and scatter angle
The carrier frequency
polarization of the transmitter and receiver
FFS Temporal or spatial consistency
FFS antenna pattern
FFS whether/how to model the above factors in the CR, e.g. with an RCS model with a scattering point

R1-2402682 Summary #3 on ISAC channel modelling Moderator (Xiaomi)

Presented in Thursday session

R1-2403715 Summary #4 on ISAC channel modelling Moderator (Xiaomi)

From Friday session

Agreement

EO is a non-target object with known location.

· FFS other known parameters of the EO

· FFS details on EO modeling

The following options for EO modeling are considered for further study

· Option 1: EO is modelled different from a sensing target

o Applicable at least for an EO having extremely large size (referred as EO type-2 for discussion purpose)

o FFS modeled similar to section 7.6.8 ground reflection in TR 38.901

o FFS EO modeling impacts the target channel and/or the background channel

· Option 2: EO is modeled same/similar as a sensing target

o Applicable for an EO having comparable physical characteristics as a sensing target, (referred as EO type-1 for discussion purpose)

o FFS Applicable for EO type-2

o FFS EO modeling impacts the target channel and/or the background channel

· Option 3: EO is modeled and its location is determined from a stochastic clutter generated following the cluster generation in TR 38.901

o FFS details

· Option 4: EO is not modelled

· Other options are not precluded

· Note: it is not precluded that multiple options can be supported in the channel modelling

Agreement

The following options are considered for further study to model the target channel for a target

· Option 1: modelled by concatenation of path(s) from Tx to target and from target to Rx

· Option 2: modelled by Tx-to-Rx path(s) satisfying Tx-target-Rx geometry

· Option 3: combination of Option 1 and Option 2

Agreement

If a target is modelled with single scattering point, the following options to model RCS of the target are considered for further study.

· Option 1: Random RCS value generated by a statistical distribution, depending on the factor(s) having impacts on the RCS modelling.

o FFS the distribution.

o FFS the factor(s)

· Option 2: Deterministic RCS value is defined by a function and/or a table, depending on the factor(s) having impacts on the RCS modelling

o Note: Constant RCS for a target type can be a special case of Option 2

o FFS the factor(s)

o FFS details of function and/or table

· Option 3: combination of Option 1 & 2, e.g., RCS value is generated by combining a deterministic component and a randomly generated component.

· FFS application of each option to large scale fading and/or small scale fading

· FFS target with multiple scattering points

Agreement

· Interested companies are encouraged to submit validation results together with their proposal for ISAC channel modeling

· Up to each company to select the way for validation

o Option 1: Experimental results

o Option 2: Experimental results to validate a ray-tracing model, then the ray-tracing based results to validate the ISAC channel model

§ Note: the layout of the scenario used for validation is up to company choice

Agreement

ISAC channel model for link level simulation is to be discussed after the system level channel model is sufficiently stable with basic functionalities.

Final summary in R1-2403716.

RAN1#117

9.7 Study on channel modelling for Integrated Sensing And Communication (ISAC) for NR

Please refer to RP-240799 for detailed scope of the SI.

R1-2405697 Session notes for 9.7 (Study on channel modelling for Integrated Sensing And Communication for NR) Ad-Hoc Chair (Huawei)

Friday decision: The session notes are endorsed and contents reflected below.

[117-R19-ISAC] – Yingyang (xiaomi)

Email discussion on Rel-19 ISAC channel model

- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2404630 Updated work plan on channel modelling for ISAC Xiaomi, AT&T

R1-2404631 Skeleton CR for TR 38.901 to introduce channel model for ISAC Xiaomi, AT&T

R1-2404822 Ray-Tracing based Channel Models for Automotive ISAC DENSO CORPORATION

9.7.1 ISAC deployment scenarios

R1-2403916 Discussion on ISAC deployment scenarios and requirements EURECOM

R1-2403920 Deployment scenarios for ISAC channel model Huawei, HiSilicon

R1-2403964 Deployment scenarios for ISAC channel modeling Intel Corporation

R1-2403994 Discussion on ISAC deployment scenarios Nokia, Nokia Shanghai Bell

R1-2404038 Discussion on ISAC deployment scenarios Spreadtrum Communications

R1-2404127 Discussion on ISAC deployment scenarios Samsung

R1-2404189 Views on Rel-19 ISAC deployment scenarios vivo

R1-2404302 Discussion on ISAC deployment scenarios Apple

R1-2404327 Discussion on ISAC deployment scenarios LG Electronics

R1-2404413 Discussion on ISAC deployment scenarios CATT, CICTCI

R1-2404435 Discussion on ISAC deployment scenarios China Telecom

R1-2404468 Discussion on ISAC deployment scenarios CMCC, China Southern Power Grid

R1-2404512 Views on ISAC Deployment Scenarios Sony

R1-2404522 Deployment Scenarios for ISAC Channel Modeling AT&T, FirstNet

R1-2404541 Deployment scenarios for integrated sensing and communication with NR NVIDIA

R1-2404573 Discussion on ISAC deployment scenarios Tiami Networks

R1-2404632 Deployment scenarios and evaluation assumptions for ISAC channel model Xiaomi

R1-2404651 Discussion on ISAC deployment scenarios InterDigital, Inc.

R1-2404723 Considerations on ISCA deployment scenarios CAICT

R1-2404875 Discussion on ISAC deployment scenarios OPPO

R1-2404914 Discussion on ISAC deployment scenarios TOYOTA InfoTechnology Center

R1-2404931 Discussion on ISAC deployment scenarios Lenovo

R1-2405002 Discussion on ISAC deployment scenarios ZTE

R1-2405009 Discussion on ISAC Deployment Scenarios Ericsson

R1-2405054 Study on deployment scenarios for ISAC channel modelling NTT DOCOMO, INC.

R1-2405094 Discussion on ISAC deployment scenario MediaTek Inc.

R1-2405115 Discussion on deployment scenarios for ISAC channel mode ITRI

R1-2405167 Discussion on ISAC deployment scenarios Qualcomm Incorporated

R1-2404486 FL Summary #1 on ISAC Deployment Scenarios Moderator (AT&T)

From Tuesday session

Agreement

For each of the sensing target deployment scenarios using the template agreed in RAN#116-bis, the following principles apply:

For defining sensing Tx and sensing Rx properties (e.g., cell layout, BS antenna height, and minimum distance), scenario parameter values for the applicable communication scenarios in 38.901 are considered as a starting point. Updates to these evaluation parameter values for ISAC scenarios will consider the following:

aerial UEs parameter values as defined in TR 36.777
indoor room scenario parameter values defined in TR 38.808
automotive scenario parameter values as defined in TR 37.885, 38.859 for Urban grid/Highway
Minimum distances between Tx/Rx and target are not defined in the existing communications scenarios and shall be included in the sensing target deployment scenarios.
Note: Only deviation from the existing evaluation parameters in the applicable communication scenarios need to be explicitly defined in the ISAC scenario tables.

For defining sensing target properties, as a baseline

Evaluation parameter values can be taken from additional TRs, e.g., TR 36.777, 37.885, 38.859, etc.
Size of sensing targets based on TR 22.837, 37.885 (e.g. for automotive), 38.901 (e.g. for AGV size), etc

Agreement

For ISAC deployment scenarios, carrier frequency, bandwidth, and SCS are not included in the evaluation parameters templates for sensing scenarios, but may be included in the evaluation/calibration phase.

R1-2404487 FL Summary #2 on ISAC Deployment Scenarios Moderator (AT&T)

From Wednesday session

Agreement

For UAV sensing target scenarios, the following table is used as a starting point for deployment scenario parameters/values.

Note: Additional parameters, value/value ranges are not precluded.

Table x. Evaluation parameters for UAV sensing scenarios

Parameters			Value
Applicable communication scenarios			UMi, UMa, RMa [38.901] UMi-AV, UMa-AV, RMa-AV
Sensing transmitters and receivers properties	Rx/Tx Locations		Rx/Tx locations are selected among the TRPs and UEs locations in the corresponding communication scenario Note1: this may include aerial UEs for UMi-AV, UMa-AV, RMa-AV communication scenarios. [In this case, other Rx/Tx properties (e.g. mobility) are also taken from the corresponding communication scenario.]


Supported sensing modes			[All 6 sensing modes]
Sensing target
		Outdoor/indoor	Outdoor
		3D mobility	Horizontal velocity: Up to 160 km/h [FFS specific velocity(ies) or random distribution] [FFS vertical plane velocity]
		3D distribution	[Uniform between a minimum and maximum height] [Uniform in horizontal domain at a given height]
		Orientation	Random in horizontal domain
		Physical characteristics (e.g., size)	UAV object type(s) [FFS]
[Sensing area]
Minimum 3D distances between pairs of Tx/Rx and sensing target/[unintended objects]			FFS
Minimum 3D distance between sensing targets			FFS
[Unintended/Environment objects, e.g., types, characteristics, mobility, distribution, etc.]			FFS

R1-2404488 FL Summary #3 on ISAC Deployment Scenarios Moderator (AT&T)

From Thursday session

Agreement (confirmed in Friday)

RAN1 agrees to the following revised evaluation parameters values for the UAV sensing target scenarios:

Parameters

Value

Sensing transmitters and receivers properties

Rx/Tx locations are selected among the TRPs and UEs locations in the corresponding communication scenario

Note 1: Other Rx/Tx properties (e.g. mobility) can also be taken from the corresponding communication scenario.

Note 2: This may include aerial UEs as Rx/Tx that can be selected among locations in the UMi-AV, UMa-AV, RMa-AV communication scenarios.

9.7.22 ISAC channel modelling

R1-2403917 Discussion on ISAC channel modeling EURECOM

R1-2403921 Channel modelling for ISAC Huawei, HiSilicon

R1-2403965 Discussion on ISAC channel modeling Intel Corporation

R1-2403995 Discussion on ISAC channel modelling Nokia, Nokia Shanghai Bell

R1-2404039 Discussion on ISAC channel modeling Spreadtrum Communications

R1-2404128 Discussion on ISAC channel modelling Samsung

R1-2404190 Views on Rel-19 ISAC channel modelling vivo

R1-2404303 Discussion on ISAC channel modelling Apple

R1-2404328 Discussion on ISAC channel modelling LG Electronics

R1-2404344 Discussions on ISAC Channel Modelling Lekha Wireless Solutions (Late submission)

R1-2404414 Discussion on ISAC channel modelling CATT, CICTCI

R1-2404417 Discussion on ISAC channel modeling BUPT, CMCC

R1-2404436 Discussion on ISAC channel modelling China Telecom

R1-2404469 Discussion on channel modeling methodology for ISAC CMCC,BUPT,SEU, PML

R1-2404477 Discussion on ISAC Channel Modelling Panasonic

R1-2404513 Views on channel modelling for ISAC Sony

R1-2404542 Channel modeling for integrated sensing and communication with NR NVIDIA

R1-2404570 Discussion on ISAC Channel Modeling Tiami Networks

R1-2404652 Discussion on ISAC channel modeling InterDigital, Inc.

R1-2404724 Considerations on ISAC channel modelling CAICT

R1-2404876 Study on ISAC channel modelling OPPO

R1-2404915 Discussion on ISAC channel modelling TOYOTA InfoTechnology Center

R1-2404924 Discussions on ISAC Channel Modeling AT&T

R1-2404926 Discussion on Channel Modelling for ISAC Lenovo

R1-2405003 Discussion on channel modelling for ISAC ZTE, BJTU

R1-2405010 Discussion on ISAC Channel Modelling Ericsson

R1-2405055 Discussion on ISAC channel modeling NTT DOCOMO, INC.

R1-2405095 Discussion on ISAC channel modelling MediaTek Inc.

R1-2405098 Discussion on ISAC channel model Xiaomi, BUPT, BJTU

R1-2405168 Discussion on ISAC channel modelling Qualcomm Incorporated

R1-2405249 Discussion on ISAC Channel Modelling CEWiT

R1-2405276 Discussions on ISAC Channel Modelling ITL

R1-2404633 Summary #1 on ISAC channel modelling Moderator (Xiaomi)

From Tuesday session

Agreement

· Multiple sensing targets can be modelled in the ISAC channel of a pair of sensing Tx and sensing Rx

o FFS whether to model a propagation path from Tx to Rx interacting with more than one sensing target

· The same sensing target can be modelled in the ISAC channels of multiple pairs of sensing Tx and Rx

Agreement

· For discussion purpose, the propagation paths in the target channel are classified

o The direct path, i.e., LOS ray from Tx to target + LOS ray from target to Rx

o The indirect paths, i.e., any propagation path other than the direct path, including

§ LOS ray from Tx to target + NLOS ray from target to Rx

§ NLOS ray from Tx to target + LOS ray from target to Rx

§ NLOS ray from Tx to target + NLOS ray from target to Rx

· For radio propagation Case 1,

o For a direct path, the following parameters are [deterministically] generated at least based on the geometry location of Tx, target and Rx

§ AoA/ZoA at Rx

§ AoD/ZoD at Tx

§ AoA/ZoA/AoD/ZoD at target

§ delay

§ FFS initial phase

§ Doppler

§ FFS power/polarization including the impact of RCS

§ FFS the number of direct path(s) for a target

o FFS on detailed modelling of indirect path(s)

· FFS on details of modelling of indirect paths in radio propagation Case 2/3/4

· To generate the channel coefficients of direct/indirect path(s) in the target channel, the channel coefficient generation function in step 11 in section 7.5 of TR 38.901 (e.g., formula 7.5-22) is used as the start point

o Note: modification to step 11 is deemed necessary

o FFS adding impact of small scale RCS

o FFS Doppler

R1-2404634 Summary #2 on ISAC channel modelling Moderator (Xiaomi)

R1-2404635 Summary #3 on ISAC channel modelling Moderator (Xiaomi)

From Thursday session

Agreement

· Spatial consistency should be supported for ISAC channel

· Spatial consistency should be supported based on movement of sensing Tx, sensing target and/or sensing Rx

o FFS EO handling

Agreement

When the stochastic cluster is used to generate the indirect paths in the target channel of a target

The stochastic cluster generation in section 7, TR 38.901 is used as starting point.

FFS a stochastic cluster is generated between Tx and Rx satisfying Tx-target-Rx geometry, or between Tx/Rx and target

FFS modification to stochastic cluster generation in section 7, TR 38.901
FFS use of sub-cluster to model the indirect paths

Note: RAN1 continues studying using EO to generate the indirect paths in the target channel of a target

Agreement

When the stochastic cluster is used to model indirect path in the target channel

For bistatic, the LOS condition from Tx to target and from target to Rx is determined separately for a target

FFS: The correlation of LOS condition of Tx-target and Rx-target links of a target

For monostatic, a same LOS condition is determined for Tx to target and target to Rx
The LOS condition from Tx to target and/or from target to Rx is determined with the LOS probability

The probability schemes in existing 3GPP TRs, e.g., TR 38.901. TR 36.777, TR 37.885, etc. are considered as start point
FFS: How to consider the impacts of target height on LOS probability.

Agreement

When stochastic cluster is used to model indirect path in the target channel, down-select between the following options

Option 1: modelled by concatenation of path(s) from Tx to target and from target to Rx

For each of the Tx-target link and target-Rx link,

The parameters delay, power, angle, [initial phase], [Doppler] of NLOS ray(s) in the link Tx-to-Target or Target to RX are generated

FFS following cluster generation in section 7, 38.901

The target channel is generated by concatenating the parameters of the Tx-target link and target-Rx link.

FFS on Convolutional or 1-by-1 coupling or 1-to-many coupling

FFS how to combine the clusters in target channel and the clusters in background channel

Option 2: modelled by Tx-to-Rx path(s) satisfying Tx-target-Rx geometry of the direct path

The parameters delay, power, angle, initial phase of a stochastic (sub-)cluster between Tx and Rx are generated following cluster generation in section 7, 38.901

The parameters [delay], [power], [angle], [Doppler] of the (sub-)cluster are updated by the target property

FFS how to combine the clusters in target channel and the clusters in background channel

Final summary in R1-2404636.

RAN1#118

9.7 Study on channel modelling for Integrated Sensing And Communication (ISAC) for NR

Please refer to RP-240799 for detailed scope of the SI.

R1-2407480 Session notes for 9.7 (Study on channel modelling for Integrated Sensing And Communication for NR) Ad-Hoc Chair (Huawei)

Friday decision: The session notes are endorsed and contents reflected below.

[118-R19-ISAC] – Yingyang (xiaomi)

Email discussion on Rel-19 ISAC channel model

- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

9.7.1 ISAC deployment scenarios

R1-2405922 Discussion on ISAC deployment scenarios Spreadtrum Communications

R1-2405999 Discussion on ISAC deployment scenarios CMCC, China Southern Power Grid

R1-2406009 Deployment scenarios for ISAC channel modeling Intel Corporation

R1-2406047 Discussion on ISAC deployment scenarios and requirements EURECOM

R1-2406067 Discussion on deployment scenarios for ISAC Tejas Network Limited

R1-2406075 Discussion on ISAC deployment scenarios KPN N.V.

R1-2406084 Discussion on ISAC deployment scenarios Tiami Networks

R1-2406098 Discussion on ISAC deployment scenarios China Telecom

R1-2406137 Discussion on ISAC deployment scenarios Nokia, Nokia Shanghai Bell

R1-2406196 Views on Rel-19 ISAC deployment scenarios vivo

R1-2406207 Discussion on ISAC deployment scenarios InterDigital, Inc.

R1-2406249 Discussion on ISAC deployment scenarios OPPO

R1-2406298 Deployment scenarios and evaluation assumptions for ISAC channel model Xiaomi

R1-2406382 Discussion on ISAC deployment scenarios CATT, CICTCI

R1-2406450 Discussion on ISAC deployment scenarios LG Electronics

R1-2406483 Discussion on ISAC deployment scenarios Sony

R1-2406488 Deployment scenarios for integrated sensing and communication with NR NVIDIA

R1-2406528 Discussion on ISAC deployment scenarios Panasonic

R1-2406529 Discussion on deployment scenarios for ISAC Hanbat National University

R1-2406664 Discussion on ISAC deployment scenarios Samsung

R1-2406715 Discussion on ISAC deployment scenarios Lenovo

R1-2406767 Discussion on ISAC deployment scenario MediaTek Inc.

R1-2406792 Discussion on ISAC deployment scenarios TOYOTA InfoTechnology Center

R1-2406856 Discussion on ISAC deployment scenarios Apple

R1-2406867 Deployment Scenarios for ISAC Channel Modeling AT&T, FirstNet

R1-2406896 Considerations on ISCA deployment scenarios CAICT

R1-2406905 Discussion on ISAC Deployment Scenarios Ericsson

R1-2406944 Study on deployment scenarios for ISAC channel modelling NTT DOCOMO, INC.

R1-2406959 Discussion on ISAC deployment scenarios ZTE Corporation, Sanechips

R1-2406974 Deployment scenarios for ISAC channel model Huawei, HiSilicon

R1-2407043 Discussion on ISAC deployment scenarios Qualcomm Incorporated

R1-2406873 FL Summary #1 on ISAC Deployment Scenarios Moderator (AT&T)

R1-2406874 FL Summary #2 on ISAC Deployment Scenarios Moderator (AT&T)

From Wednesday session

Conclusion

RAN1 will consider the recommendations for the physical characteristics (e.g., sizes, shapes, materials, velocities, etc.) of sensing targets and objects provided in 5GAA LS (R1-2405964), along with the relevant characteristics defined in 3GPP TRs, within the scope of the Rel-19 study item.

· No LS response from RAN1 to 5GAA is necessary.

· R1-2405964 is proposed to be NOTED.

Agreement

General principles for all sensing target deployment scenarios should consider the following:

· “Sensing mode” is removed in the scenario tables, but may be included in the evaluation/calibration phase. Per the SI, all sensing modes are possible for the deployment scenarios.

· “Sensing area” may be addressed as part of the sensing target distribution and/or Tx/Rx characteristics and/or cell layout.

R1-2406875 FL Summary #3 on ISAC Deployment Scenarios Moderator (AT&T)

From Thursday session

Agreement

For UAV sensing target scenarios, the following table is agreed for deployment scenario parameters/values using the agreements from RAN1#117 as a baseline.

Note: Additional parameters, value/value ranges are not precluded.

The detailed scenario description in this clause can be used for channel model calibration.

ISAC-UAV

Details on ISAC-UAV scenarios are listed in Table x.

Table x. Evaluation parameters for UAV sensing scenarios

Parameters		Value
Applicable communication scenarios		UMi, UMa, RMa [38.901] UMi-AV, UMa-AV, RMa-AV
Sensing transmitters and receivers properties	Rx/Tx Locations	Rx/Tx locations are selected among the TRPs and UEs locations in the corresponding communication scenarios. Note1: This may include aerial UEs for UMi-AV, UMa-AV, RMa-AV communication scenarios. In this case, other Rx/Tx properties (e.g. mobility) are also taken from the corresponding communication scenario.
Sensing target	Outdoor/indoor	Outdoor
	3D mobility	Horizontal velocity: uniform distribution between 0 and 180km/h, if horizontal velocity is not fixed to 0. Vertical velocity: 0km/h, optional {20, 40} km/h NOTE2: 3D mobility can be horizontal only or vertical only or a combination for each sensing target FFS: time-varying velocity.
	3D distribution	Horizontal plane: Option A: N targets uniformly distributed within one cell. Option B: N targets uniformly distributed per cell. Option C: N targets uniformly distributed within an area not necessarily determined by cell boundaries. FFS: Value of N, defined area, and other distributions Vertical plane: Option A: Uniform between 1.5m and 300m. Option B: Fixed height value chosen from {25, 50, 100, 200, 300} m assuming vertical velocity is equal to 0. FFS Other options are not precluded. Note2: target(s) are outside the minimum distance to the Tx/Rx
	Orientation	Random in horizontal domain
	Physical characteristics (e.g., size)	Size: · Option 1: 1.6m x 1.5m x 0.7m · Option 2: 0.3m x 0.4m x 0.2m FFS: Material(s), Structure, Other size(s)
Minimum 3D distances between pairs of Tx/Rx and sensing target		Option B: Min distances based on min. TRP/UE distances defined in TR36.777 as a starting point. Option C: Min. distance is larger than the min. far-field distance of the sensing Tx/Rx
Minimum 3D distance between sensing targets		Option 1: At least larger than the physical size of a target Option 2: 10 meters
[Unintended/Environment objects, e.g., types, characteristics, mobility, distribution, etc.]		FFS

Note: further down-selection between the options in the table is not precluded.

9.7.22 ISAC channel modelling

R1-2405923 Discussion on ISAC channel modeling Spreadtrum Communications

R1-2406000 Discussion on channel modeling methodology for ISAC CMCC,BUPT,SEU, PML

R1-2406010 Discussion on ISAC channel modeling Intel Corporation

R1-2406048 Discussion on ISAC channel modeling EURECOM

R1-2406066 Discussion on ISAC channel modelling Tejas Network Limited

R1-2406085 Discussion on ISAC Channel Modeling Tiami Networks

R1-2406099 Discussion on ISAC channel modelling China Telecom

R1-2406107 ISAC Channel Measurements and Modeling BUPT, CMCC, VIVO

R1-2406138 Discussion on ISAC channel modelling Nokia, Nokia Shanghai Bell

R1-2407211 Views on Rel-19 ISAC channel modelling vivo, BUPT (rev of R1-2406197)

R1-2406208 Discussion on ISAC channel modeling InterDigital, Inc.

R1-2406211 Measurement-Based EO Study and Multi-Dimensional Target Modeling NIST

R1-2407200 Study on ISAC channel modelling OPPO (rev of R1-2406250)

R1-2406383 Discussion on ISAC channel modelling CATT, CICTCI

R1-2406451 Discussion on ISAC channel modelling LG Electronics

R1-2406484 Discussion on Channel Modelling for ISAC Sony

R1-2406489 Channel modeling for integrated sensing and communication with NR NVIDIA

R1-2406530 Discussion on channel modelling for ISAC Hanbat National University

R1-2406665 Discussion on ISAC channel modelling Samsung

R1-2406698 Channel modeling methodology updates for ISAC Keysight Technologies UK Ltd

R1-2406710 Discussion on ISAC channel model Xiaomi, BJTU

R1-2406713 Discussion on ISAC Channel Modelling Panasonic

R1-2406714 Discussion on Channel Modelling for ISAC Lenovo

R1-2406768 Discussion on ISAC channel modelling MediaTek Inc.

R1-2406793 Discussion on ISAC channel modelling TOYOTA InfoTechnology Center

R1-2406799 General Requirements for Automotive ISAC DENSO CORPORATION Late submission

R1-2406857 Discussion on ISAC channel modelling Apple

R1-2406868 Discussions on ISAC Channel Modeling AT&T

R1-2406897 Considerations on ISAC channel modelling CAICT

R1-2406906 Discussion on ISAC Channel Modelling Ericsson

R1-2406945 Discussion on ISAC channel modeling NTT DOCOMO, INC.

R1-2406960 Discussion on channel modelling for ISAC ZTE Corporation, Sanechips

R1-2406975 Channel modelling for ISAC Huawei, HiSilicon

R1-2407044 Discussion on ISAC channel modelling Qualcomm Incorporated

R1-2407092 Discussion on ISAC Channel Modelling CEWiT

R1-2406299 Summary #1 on ISAC channel modelling Moderator (Xiaomi)

From Monday session

Agreement

If RCS related coefficient of a scattering point is included in small scale, the RCS related coefficients are separately determined for different pairs of incident/scattered ray(s) at the scattering point.

Agreement

For radio propagation Case 1, for modelling the target channel of a target with single scattering point,

· To model a direct path, a single LOS ray from Tx to target and a single LOS ray from target to Rx are generated

o AoA/ZoA of the direct path at Rx, AoD/ZoD of the direct path at target are generated at least based on the 3D location of target and Rx in the global coordinate system

o AoD/ZoD of the direct path at Tx, AoA/ZoA of the direct path at target are generated at least based on the 3D location of Tx and target in the global coordinate system

o The Delay of the direct path = (d3D_tx_target + d3D_target_rx)/c

o The Doppler of the direct path is generated by spherical unit vectors by AoD/ZoD at Tx, by spherical unit vectors by AoA/ZoA at Rx, and velocity of Tx, target and Rx

o The power of the direct path is generated as the product of the power of the LOS ray from Tx to target, the power of the LOS ray from target to Rx, and the effect of RCS

o FFS initial phase

o FFS how to model RCS, polarization of target

· FFS number of direct paths

· FFS on detailed modelling of indirect path(s)

· FFS applicability of direct path generation to each scattering point when the target is modelled as multiple scattering points

R1-2406300 Summary #2 on ISAC channel modelling Moderator (Xiaomi)

From Wednesday session

Agreement

For the target channel of a target with single scattering point, when stochastic cluster is used to model an indirect path in the target channel,

An indirect path in small scale is modelled by concatenation of path(s) from Tx to target and from target to Rx, i.e., Option 1 in the agreement of RAN1 #117

AoD/ZoD/AoA/ZoA from Tx to target or from target to Rx are

generated for a LOS ray at least based on the 3D location of Tx/Rx and target in the global coordinate system
stochastically generated for a NLOS ray using section 7, 38.901 as starting point

Delay is sum of delay of LOS/NLOS ray from Tx to target and the LOS/NLOS ray from target to Rx
Doppler is generated by spherical unit vector by AoD/ZoD at Tx and velocity of Tx, by spherical unit vector by AoA/ZoA at Rx and velocity of Rx, and by spherical unit vectors by AoA/ZoA/AoD/ZoD at target and velocity of target

FFS The mobility of stochastic clutter

The power of the indirect path is generated as the product of the power of the LOS/NLOS ray from Tx to target, the power of the LOS/NLOS ray from target to Rx and the effect of RCS
FFS initial phase
FFS how to model effect of RCS at target
FFS whether/how to model polarization at target
FFS How to reduce complexity
FFS applicability of the indirect path generation to each/a single scattering point when the target is modelled as multiple scattering points

R1-2406301 Summary #3 on ISAC channel modelling Moderator (Xiaomi)

From Thursday session

Working assumption

The RCS related coefficient of a scattering point can be modelled with two components, i.e., linear value RCS = A*B

A first RCS component A () is included in large scale

FFS the first RCS component is deterministic or stochastic
FFS The first component is dependent on incident and scattered directions at target

A second RCS component B (unit ratio) is included in small scale

FFS The second component is dependent on incident and scattered directions at target
FFS the second RCS component is deterministic or stochastic or combination

Note: RCS component A or B can be disabled by setting its linear value to 1

Whether to disable a component can be discussed per target type

FFS how to determine A and B for each target
FFS whether/how to model polarization impact at target
FFS whether/how to normalize power accounting for target channel and background channel

Agreement

The impact of a scattering point of the target in the target channel is modelled by a scalar RCS value times a complex-valued 2x2 polarization matrix , i.e.,

· FFS whether is angular/ray-dependent or independent.

· FFS whether polarization matrix is modelled assuming specular reflection or random coefficient for diffraction or scattering.

· FFS whether polarization matrix is explicitly modelled or merged with other polarization matrixes from Tx to target and/or from target to Rx.

Agreement

For modeling stochastic cluster in background channel, in order to define the background channel for TRP-UE and UE-TRP bistatic sensing mode,

The large scale and small scale parameters defined in TR 38.901, TR 37.885, TR 36.777 are used as start point

In order to define the background channel for TRP-TRP and UE-UE bistatic sensing mode,

RAN1 to study how to model background channel

Option 1: The large scale and small scale parameters defined in TR 38.901, TR 38.858, 37.885, 38.859 are used as start point.
Option 2: New channel model based on measurement results or ray-tracing model validated by experimental results.

FFS whether/how to do power normalization between target channel and background channel.

Agreement

In order to define the background channel for TRP and UE mono-static sensing mode,

RAN1 to study how to model the background channel

Option 1: randomly drop at least one virtual Rx, and then the background channel is generated based on the channel generated as TR 38.901 between the real Tx and each virtual Rx for a scenario.

FFS EO is modelled in the background channel.

Option 2: New channel model based on measurement results or ray-tracing model validated by experimental results or radar literatures.

FFS EO is modelled in the background channel.

Option 3: the locations of clusters in the target channel are deterministically generated, then the background channel is generated using the clusters with the determined locations.
Other options are not precluded.

Agreement

When EO type-2 is modelled, specular reflection is considered to model EO type-2 using section 7.6.8 of TR 38.901 as reference

As starting point, the effect of type-2 EO (i.e., in the path node1-EO-node2) is modelled as , b is a scaling factor (e.g., c equals to relative to LOS ray in section 7.6.8 in TR 38.901)

FFS any update to
FFS any update taking EO orientation into account

FFS any changes based on section 7.6.8 of TR 38.901 if EO type-2 has finite size
FFS whether diffraction and scattering can be considered in addition to specular reflection
EO type-2 is an optional modelling component if supported in a sensing scenario

FFS which deployment scenario(s) EO type-2 will apply

Final summary in R1-2406302.

RAN1#118-bis

9.7 Study on channel modelling for Integrated Sensing And Communication (ISAC) for NR

Please refer to RP-242348 for detailed scope of the SI.

R1-2409224 Session notes for 9.7 (Study on channel modelling for Integrated Sensing And Communication for NR) Ad-Hoc Chair (Huawei)

Friday decision: The session notes are endorsed and contents reflected below.

[118bis-R19-ISAC] – Yingyang (Xiaomi)

Email discussion on Rel-19 ISAC channel model

- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2408097 Updated work plan on channel modelling for ISAC Xiaomi, AT&T

From AI 5

R1-2407602 LS on Channel Measurements and Modeling for Joint/Integrated Communication and Sensing, as well as 7-24 GHz Communication ATIS’ Next G Alliance

Decision: To be taken into account as part of discussions in agenda item 9.7.

9.7.1 ISAC deployment scenarios

R1-2407651 Deployment scenarios for ISAC channel model Huawei, HiSilicon

R1-2407717 Discussion on ISAC deployment scenarios Spreadtrum Communications

R1-2407741 Discussion on ISAC deployment scenarios China Telecom

R1-2407750 ISAC deployment scenarios Tejas Network Limited

R1-2407872 Views on Rel-19 ISAC deployment scenarios vivo

R1-2407916 Discussion on ISAC deployment scenarios CMCC, China Southern Power Grid

R1-2407980 Deployment scenarios and evaluation assumptions for ISAC channel model Xiaomi

R1-2408058 Discussion on ISAC deployment scenarios CATT, CICTCI

R1-2408092 Discussion on ISAC deployment scenarios and requirements EURECOM

R1-2408154 Discussion on ISAC deployment scenarios OPPO

R1-2408240 Deployment scenarios for ISAC study KRRI, Hanbat National University

R1-2408274 Discussion on ISAC deployment scenarios TOYOTA InfoTechnology Center

R1-2408303 Discussion on ISAC deployment scenarios LG Electronics

R1-2408315 Discussion on ISAC Deployment Scenarios Nokia, Nokia Shanghai Bell

R1-2408340 Discussion on ISAC Deployment Scenarios Ericsson

R1-2408386 Deployment scenarios for integrated sensing and communication with NR NVIDIA

R1-2408419 Considerations on ISAC deployment scenarios Sony

R1-2408482 Discussion on ISAC deployment scenarios Apple

R1-2408514 Discussion on ISAC deployment scenarios ZTE Corporation, Sanechips

R1-2408523 Discussion on ISAC deployment scenarios InterDigital, Inc.

R1-2408534 Discussion on ISAC deployment scenarios Panasonic

R1-2408657 Discussion on ISAC deployment scenarios Samsung

R1-2408710 Discussion on ISAC deployment scenario MediaTek Inc.

R1-2408720 Discussion on ISAC deployment scenarios Tiami Networks

R1-2408746 Discussion on ISAC deployment scenarios Lenovo

R1-2408755 Deployment Scenarios for ISAC Channel Modeling AT&T, FirstNet

R1-2408797 Study on deployment scenarios for ISAC channel modelling NTT DOCOMO, INC.

R1-2408809 Considerations on ISAC deployment scenarios CAICT

R1-2408861 Discussion on ISAC deployment scenarios Qualcomm Incorporated

R1-2408904 Evaluation Parameters for ISAC in Automotive Scenarios Continental Automotive

R1-2408760 FL Summary #1 on ISAC Deployment Scenarios Moderator (AT&T)

From Tuesday session

Agreement

For Automotive sensing target scenarios, the following table is used as a starting point for deployment scenario parameters/values.

The detailed scenario description in this clause can be used for channel model calibration.

Note: Additional parameters, value/value ranges are not precluded.

Table x. Evaluation parameters for Automotive sensing scenarios

Parameters		Values
Applicable communication scenarios		Highway, Urban Grid. NOTE1
Sensing transmitters and receivers properties		Rx/Tx locations are selected among the TRPs and UEs (e.g., VRU, vehicle, RSU-type UEs) locations in the corresponding communication scenario. NOTE2 FFS: Option 2: ISD between TRPs of Urban Grid is 250 meters
Sensing target	LOS/NLOS	LOS and NLOS (including NLOSv)
	Outdoor/indoor	Outdoor
	Mobility (horizontal plane only)	Based on TR37.885 mobility for urban grid or highway scenario
	Distribution (horizontal)	Based on dropping in TR37.885 per urban grid or highway communication scenario
	Orientation	Lane direction in horizontal plane
	Physical characteristics (e.g., size)	Type 1/2 (passenger vehicle) Type 3 (truck/bus) Vehicle type distribution per TR 37.885 as a starting point FFS: Other sizes, additional distributions, and vehicle types, e.g. one new type of e-scooter/motorcycle/bike
Minimum 3D distances between pairs of Tx/Rx and sensing target		Option 1: Min distances based on min. TRP/UE distances defined in TR37.885 as a starting point. Option 2: Min. distance is larger than the min. far-field distance of the sensing Tx/Rx
Minimum 3D distance between sensing targets		Option 1: At least larger than the physical size of a sensing target Option 2: Fixed value, [x] m. value of x is FFS
Environment Objects, e.g., types, characteristics, mobility, distribution, etc.		EO Type 2 for Urban Grid · FFS: details, e.g. 4 walls (as EO type 2) per building of size [413mx230mx20m]

NOTE1: calibration for UMi, Uma, RMa is not performed for the automotive scenario, but UMi, Uma, RMa can be considered for future evaluations of the automotive sensing target scenarios. Calibration for UMi, Uma, RMa is expected to be performed for another sensing scenario.

NOTE2: A percentage of TRPs/UEs that have sensing capabilities may be considered for future evaluations.

R1-2408761 FL Summary #2 on ISAC Deployment Scenarios Moderator (AT&T)

From Wednesday session

Agreement

For Human sensing target scenarios, (indoor and outdoor), the following table is used as a starting point for deployment scenario parameters/values.

The detailed scenario description in this clause can be used for channel model calibration.

Note: Additional parameters, value/value ranges are not precluded.

Table x. Evaluation parameters for Human (indoor and outdoor) sensing scenarios

Parameters		Indoor Values	Outdoor Values
Applicable communication scenarios NOTE1		Indoor office, indoor factory [TR38.901] Indoor room [TR38.808]	UMi, Uma, RMa [TR38.901]
Sensing transmitters and receivers properties	Rx/Tx Locations NOTE 2	Rx/Tx locations are selected among the TRPs and UE locations in the corresponding communication scenario	Rx/Tx locations are selected among the TRPs and UE locations in the corresponding communication scenario
Sensing transmitters and receivers properties	Rx/Tx Mobility for UEs	Option 1: 0km/h Option 2: 3km/h Option 3: Uniform distribution between 0km/h and 3km/hr	Option 1: 0km/h Option 2: 3km/h Option 3: Uniform distribution between 0km/h and 10km/hr
Sensing target	Outdoor/indoor	Indoor	Outdoor
	3D mobility	Option 1: 0km/h Option 2: 3km/h Option 3: Uniform distribution between 0km/h and 3km/hr (horizontal plane with random direction straight-line trajectory)	Option 1: 0km/h Option 2: 3km/h Option 3: Uniform distribution between 0km/h and 10km/hr (horizontal plane with random direction straight-line trajectory)
	3D distribution	N targets uniformly distributed over the horizontal area of the convex hull of the TRP deployment FFS: Value of N	Uniform in horizontal plane
	Orientation	Random over the horizontal area	Random over the horizontal area
	Physical characteristics (e.g., size)	Size (Length x Width x Height): · Child: 0.2m x 0.3m x 1m · Adult Pedestrian: 0.5m x 0.5m x 1.75m	Size (Length x Width x Height): · Child: 0.2m x 0.3m x 1m · Adult Pedestrian: 0.5m x 0.5m x 1.75m
Minimum 3D distances between pairs of Tx/Rx and sensing target		Option 1: Min. distance is larger than the min. far-field distance of the sensing Tx/Rx Option 2: Min distances defined in TR 38.901 as a starting point	Option 1: Min. distance is larger than the min. far-field distance of the sensing Tx/Rx Option 2: Min distances defined in TR 38.901 as a starting point
Minimum 3D distance between sensing targets		Option 1: At least larger than the physical size of a sensing target Option 2: Fixed value, [x] m. value of x is FFS	Option 1: At least larger than the physical size of a sensing target Option 2: Fixed value, [x] m. value of x is FFS
Environment Objects, e.g., types, characteristics, mobility, distribution, etc.		FFS, based on outcome for AI 9.7.2	FFS, based on outcome for AI 9.7.2

NOTE1: For the human (indoor and outdoor) sensing targets, additional communication scenarios can be considered for future evaluations. Channel model calibration for Urban Grid with outdoor humans is expected to be performed from Objects creating hazards on the road/railway sensing scenarios.

NOTE2: A percentage of TRPs/UEs that have sensing capabilities may be considered for future evaluations.

R1-2408762 FL Summary #3 on ISAC Deployment Scenarios Moderator (AT&T)

From Thursday session

Agreement

For Automated Guided Vehicles (AGV) target scenarios, the following table is used as a starting point for deployment scenario parameters/values.

The detailed scenario description in this clause can be used for channel model calibration.

Note: Additional parameters, value/value ranges are not precluded.

Table x. Evaluation parameters for Automated Guided Vehicles

Parameters		Value
Applicable communication scenarios NOTE1		InF (TR38.901 including Table 7.8-7)
Sensing transmitters and receivers properties NOTE2		Rx/Tx location are selected among the TRPs and UEs location in the corresponding communication scenario Rx/Tx Mobility for UEs - Option 1: 0 km/h - Option 2: 3km/h - Option 3: Uniform distribution between 0km/h and 3km/h
Sensing target	LOS/NLOS	LOS and NLOS
	Outdoor/indoor	Indoor
	3D mobility	Horizontal velocity with random straight-line trajectory - Option 1: Uniform distribution in the range of up to 30 km/h - Option 2: Fixed velocities [3, 10] km/h
	3D distribution	Option A: Uniformly distributed in the convex hull of the horizontal BS deployment Option B: Uniformly distributed in horizontal plane
	Orientation	Horizontal plane only
	Physical characteristics (e.g., size)	Size (L x W x H) - Option 1: 0.5m x 1.0m x 0.5m - Option 2: 1.5 m x 3.0m x 1.5 m - FFS: Material, Additional sizes, and AGV size distribution
Minimum 3D distances between pairs of Tx/Rx and sensing target		Option 1: Min. distance is larger than the min. far-field distance of the sensing Tx/Rx from the sensing target Option 2: Min distances based on min. TRP/UE distances defined in TR38.901
Minimum 3D distance between sensing targets		Option A: At least larger than the physical size of a target Option B: Fixed value, [x] m. value of x is FFS
Environment objects, e.g., types, characteristics, mobility, distribution, etc.		FFS

NOTE1: For the AGV sensing targets, additional communication scenarios can be considered for future evaluations.

NOTE2: A percentage of TRPs/UEs that have sensing capabilities may be considered for future evaluations.

NOTE3: RAN1 can further discuss narrowing down the number of sub-scenarios of InF

Agreement

For objects creating hazards, the following proposals are suggested to be discussed by RAN1:

For objects creating hazards use cases, RAN1 to consider the following table as a starting point for deployment scenario parameters/values.

The detailed scenario description in this clause can be used for channel model calibration.

Note: Additional parameters, value/value ranges are not precluded.

Table x. Evaluation parameters for objects creating hazards

Parameters		Value
Applicable communication scenarios NOTE1		Highway, Urban grid, HST (High Speed Train)
Sensing transmitters and receivers properties NOTE2	Rx/Tx Locations	Rx/Tx locations are selected among the TRPs and UEs (e.g., VRU, vehicle, RSU-type UEs) locations in the corresponding communication scenarios. FFS: Option 2: ISD between TRPs of Urban Grid is 250 meters
Sensing target	LOS/NLOS	LOS and NLOS
	Outdoor/indoor	Outdoor
	3D mobility	Horizontal velocity: up to [10] km/h for humans and animals FFS: Additional velocities, trajectory
	3D distribution	Uniformly distributed in horizontal plane
	Orientation	Random distribution in horizontal plane
	Physical characteristics (e.g., size)	For human/pedestrians: Child: 0.2m x 0.3m x 1m Adult: 0.5m x 0.5m x 1.75m For animals: Size: 1.5m x 0.5m x 1 m FFS: other types of targets
Minimum 3D distances between pairs of Tx/Rx and sensing target		Option 1: Min. distance is larger than the min. far-field distance of the sensing Tx/Rx from the sensing target Option 2: based on TR37.885 and TR38.802
Minimum 3D distance between sensing targets		Option 1: At least larger than the physical size of a target Option 2: Fixed value, [x] m. value of x is FFS
Environment objects, e.g., types, characteristics, mobility, distribution, etc.		EO Type 2 for Urban Grid · FFS: details, e.g. 4 walls (as EO type 2) per building of size [413mx230mx20m]

NOTE1: For the objects creating hazards sensing targets, additional communication scenarios can be considered for future evaluations.

NOTE2: A percentage of TRPs/UEs that have sensing capabilities may be considered for future evaluations.

9.7.22 ISAC channel modelling

R1-2407652 Channel modelling for ISAC Huawei, HiSilicon

R1-2407718 Discussion on ISAC channel modeling Spreadtrum Communications

R1-2407742 Discussion on ISAC channel modelling China Telecom

R1-2407751 ISAC channel modelling Tejas Network Limited

R1-2407873 Views on Rel-19 ISAC channel modelling vivo, BUPT

R1-2407917 Discussion on channel modeling methodology for ISAC CMCC,BUPT,SEU, PML

R1-2408059 Discussion on ISAC channel modelling CATT, CICTCI

R1-2408093 Discussion on ISAC channel modeling EURECOM

R1-2408094 Discussion on ISAC channel model Xiaomi, BJTU, BUPT

R1-2408155 Study on ISAC channel modelling OPPO

R1-2408241 Channel modelling for ISAC study KRRI, Hanbat National University

R1-2408263 ISAC Channel Modeling and Measurement Validation BUPT, CMCC

R1-2408275 Discussion on ISAC channel modelling TOYOTA InfoTechnology Center

R1-2408285 Discussion on ISAC channel modeling Intel Corporation

R1-2408304 Discussion on ISAC channel modelling LG Electronics

R1-2408307 Discussions on ISAC Channel Modelling Lekha Wireless Solutions

R1-2408316 Discussion on ISAC channel modeling Nokia, Nokia Shanghai Bell

R1-2409011 Discussion on ISAC Channel Modelling Ericsson (rev of R1-2408341)

R1-2408387 Channel modeling for integrated sensing and communication with NR NVIDIA

R1-2408420 Views on Channel Modelling for ISAC Sony

R1-2408483 Discussion on ISAC channel modelling Apple

R1-2408515 Discussion on channel modelling for ISAC ZTE Corporation, Sanechips

R1-2408524 Discussion on ISAC channel modeling InterDigital, Inc.

R1-2408658 Discussion on ISAC channel modelling Samsung

R1-2408711 Discussion on ISAC channel modelling MediaTek Inc.

R1-2408721 Discussion on ISAC Channel Modeling Tiami Networks

R1-2408724 Discussion on ISAC Channel Modeling NIST

R1-2408747 Discussion on Channel Modelling for ISAC Lenovo

R1-2408756 Discussions on ISAC Channel Modeling AT&T

R1-2408798 Discussion on ISAC channel modeling NTT DOCOMO, INC.

R1-2408810 Considerations on ISAC channel modelling CAICT

R1-2408862 Discussion on ISAC channel modelling Qualcomm Incorporated

R1-2408883 Discussion on ISAC Channel Modelling Panasonic

R1-2408985 Discussion on Channel Measurements and Modeling for Integrated Monostatic Sensing and Communication Southeast University, Purple Mountain Laboratories

R1-2408098 Summary #1 on ISAC channel modelling Moderator (Xiaomi)

From Tuesday session

Agreement

RAN1 strives to define a single option per target per monostatic/bistatic sensing mode from the following two options to generate RCS values/patterns for a scattering point of a target.

· Option 2: The RCS=A*B of a scattering point can be generated by

o The component A is commonly applied to any incident/scattered angles at the scattering point

§ A is [mean] RCS value. FFS value(s) A

· Note: Mean RCS value is defined as the mean value of the distribution of RCS

o The component B

§ B is generated by [log-normal] distribution, the related [log-normal] distribution has mean μ=1 and variance V, FFS σ²

· B is separately generated for each direct/indirect path at the scattering point. FFS correlation dependent on the incident/scattered angles of the direct/indirect paths

o FFS whether/how power of all generated direct/indirect paths need to be normalized considering impact of RCS

· Option 3: The RCS=A*B=A*B1*B2 of a scattering point can be generated by

o The component A is commonly applied to any incident/scattered angles at the scattering point

§ FFS: A = 1 m² or [mean] RCS value

· Note: Mean RCS value is defined as the mean value of the distribution of RCS

o The component B is further split into B1, B2, i.e., B=B1*B2

§ B1 is deterministic based on incident/scattered angles

· FFS: B1 is defined by a function or by a table

§ B2 is generated by [log-normal] distribution, the related [log-normal] distribution has mean μ=1 and variance V, FFS σ²

· B2 is separately generated for each direct/indirect path at the scattering point. FFS correlation dependent on the incident/scattered angles of the direct/indirect paths

o FFS whether/how power of all generated direct/indirect paths need to be normalized considering impact of RCS

R1-2408099 Summary #2 on ISAC channel modelling Moderator (Xiaomi)

From Wednesday session

Agreement

RCS Option 3 is selected to model RCS of UAV with single scattering point for monostatic

· B2 of UAV is modelled using log-normal distribution for monostatic

· Different mean RCS values can be supported for UAV due to different size, shape, frequency, etc.

· For UAV of small size (option 2 for UAV size in UAV parameters table)

o B1=1

o A is mean RCS value

· For UAV of large size (option 1 for UAV size in UAV parameters table)

o B1 have dependency on incident/scattered angles

o A is mean RCS value

Agreement

To model the effect of polarization for each direct/indirect path:

Polarization of a direct/indirect path is product of polarization matrix of Tx-target link, the target, and the target-Rx link

Total polarization of a direct/indirect path is CPM_tx,sp,rx= CPM_sp,rx . CPM_sp . CPM_tx,_sp

For a LOS ray from Tx to target or from target to Rx, for CPM_tx,sp or CPM_sp,rx
For a NLOS ray generated by a stochastic cluster from Tx to target or from target to Rx, CPM_tx,sp or CPM_sp,rx is generated by XPR ratio k and initial random phases referring to TR 38.901 as start point
FFS how to normalize on CPM_tx,sp,rx
FFS CPM_sp of a scattering point of the target

FFS: how to model the effect of polarization when EO type-2 is present.

R1-2408100 Summary #3 on ISAC channel modelling Moderator (Xiaomi)

R1-2408101 Summary #4 on ISAC channel modelling Moderator (Xiaomi)

From Thursday session

Agreement

A single direct path is modeled for a scattering point of target

In each of the Tx-target and target RX links, the first NLOS cluster is generated with same delay as the LOS ray (when the absolute delay modelling of as in section 7.6.9, TR 38.901 is not applied) and with the same direction as the LOS ray.

FFS how to generate NLOS cluster when is applied.

Agreement

In order to generate each of the Tx-target link and target-Rx link in the target channel, the large scale and small scale parameters defined in existing 3GPP TRs, e.g., TR 38.901. TR 36.777, TR 37.885, TR 38.858, TR 38.859, TR 38.802, TR 38.854, etc. are used as starting point.

Agreement

On the background channel for TRP-TRP and UE-UE bistatic sensing mode, the large scale and small scale parameters defined in TR 38.901, TR 38.858, 37.885, 38.859 are used as starting point.

Update on values of the LSP/SSP parameters can be discussed based on validation data acquired by measurement or ray-tracing model.

FFS The power threshold for removing clusters in step 6, i.e., -25 dB is revised to X<-25 dB. FFS X.

FFS whether/how to resolve the inconsistency between TRP-TRP channel according to TR 38.858 and the TRP-target (UAV) channel according to TR 36.777 when UAV and TRP are set to same height.

Agreement

3D spatial consistency needs to be studied for at least UAV scenario.

Agreement

In LOS condition between sensing Tx/Rx and target, the power of LOS ray is generated following power of LOS ray in TR 38.901.

Agreement

The following options are to be studied for the concatenation of Tx-target and target-Rx link in the target channel

Direct path (if present) is always kept
Indirect paths of LOS+NLOS, NLOS+LOS (if present) are generated
On other indirect paths of NLOS + NLOS

Option 0: ray level full convolution between Tx-target link and target-Rx link for radio propagation Case 1/2/3/4
Option 0A: ray level full convolution between Tx-target link and target-Rx link only for radio propagation Case 4
Option 1: cluster level full convolution between Tx-target link and target-Rx link, then 1-by-1 coupling rays within each pair of clusters for radio propagation Case 1/2/3/4
Option 1A: cluster level full convolution between Tx-target link and target-Rx link, then 1-by-1 coupling rays within each pair of clusters only for radio propagation Case 4
Option 2: cluster level 1-by-1 coupling between Tx-target link and target-Rx link, then 1-by-1 coupling rays within each pair of clusters for radio propagation Case 1/2/3/4
Option 2A: cluster level 1-by-1 coupling between Tx-target link and target-Rx link, then 1-by-1 coupling rays within each pair of clusters only for radio propagation Case 4
Option 3: ray level 1-by-1 coupling between Tx-target link and target-Rx link for radio propagation Case 1/2/3/4
Option 3A: ray level 1-by-1 coupling between Tx-target link and target-Rx link only for radio propagation Case 4

Note: reducing the number of rays per cluster and/or reducing the number of clusters can be considered for the options above
Any indirect path with power metric less than [threshold] is dropped

the power metric of a path is the product of power of a ray in Tx-target link, power of a ray in target-Rx link and RCS of the pair of rays
FFS power normalization of target channel after path dropping
FFS the set of remaining indirect paths can be updated during movement of Tx, target or Rx

Final summary in R1-2409280.

RAN1#119

9.7 Study on channel modelling for Integrated Sensing And Communication (ISAC) for NR

Please refer to RP-242348 for detailed scope of the SI.

R1-2410846 Session notes for 9.7 (Study on channel modelling for Integrated Sensing And Communication for NR) Ad-Hoc Chair (Huawei)

Friday decision: The session notes are endorsed and contents reflected below.

[119-R19-ISAC] – Yingyang (xiaomi)

Email discussion on Rel-19 ISAC channel model

- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

9.7.1 ISAC deployment scenarios

R1-2409393 Deployment scenarios for ISAC channel model Huawei, HiSilicon

R1-2409471 Discussion on ISAC deployment scenarios and requirements EURECOM

R1-2409523 Discussion on ISAC deployment scenarios CMCC, China Southern Power Grid

R1-2409608 Discussion on ISAC deployment scenarios Samsung

R1-2409692 Views on Rel-19 ISAC deployment scenarios vivo

R1-2409717 Discussion on ISAC deployment scenarios TOYOTA InfoTechnology Center

R1-2409766 Discussion on ISAC Deployment Scenarios Nokia, Nokia Shanghai Bell

R1-2409776 Deployment scenarios for integrated sensing and communication with NR NVIDIA

R1-2409817 Discussion on ISAC deployment scenarios Apple

R1-2409836 Discussion on ISAC deployment scenarios LG Electronics

R1-2409846 Discussion on ISAC deployment scenarios InterDigital, Inc.

R1-2409907 Deployment scenarios and evaluation assumptions for ISAC channel model Xiaomi

R1-2409952 Discussion on ISAC deployment scenarios CATT, CICTCI

R1-2410006 Discussion on ISAC deployment scenarios China Telecom

R1-2410097 Discussion on ISAC deployment scenarios OPPO

R1-2410125 Discussion on ISAC Deployment Scenarios Ericsson

R1-2410162 ISAC deployment scenarios Tejas Networks Limited

R1-2410234 Considerations on ISAC deployment scenarios Sony

R1-2410322 Discussion on ISAC deployment scenarios Lenovo

R1-2410332 ISAC channel model calibration and scenario parameters AT&T, FirstNet

R1-2410369 Considerations on ISCA deployment scenarios CAICT

R1-2410400 Study on deployment scenarios for ISAC channel modelling NTT DOCOMO, INC.

R1-2410447 Discussion on ISAC deployment scenarios ZTE Corporation, Sanechips

R1-2410489 Discussion on ISAC deployment scenarios Qualcomm Incorporated

R1-2410524 Discussion on ISAC deployment scenario MediaTek Inc.

R1-2410626 Discussion on ISAC deployment scenarios Tiami Networks

R1-2410627 Discussion on ISAC channel modeling Tiami Networks

R1-2410337 FL Summary #1 on ISAC Deployment Scenarios Moderator (AT&T)

From Tuesday session

Guidance for further work

1. Rapporteurs are encouraged to start providing a draft CR for both agendas to RAN1#120.

2. Jerome to provide an initial proposal for calibrations discussions by the end of RAN1#119.

3. RAN1 agenda will clarify that input on calibrations discussions is to be provided to agenda 9.7.1 starting at RAN1#120.

Agreement

For UAV sensing target scenarios, the following table is agreed for deployment scenario parameters/values using the agreements from RAN1#118 as a baseline:

The detailed scenario description in this clause can be used for channel model calibration.

ISAC-UAV

Details on ISAC-UAV scenarios are listed in Table x.

Table x. Evaluation parameters for UAV sensing scenarios

Parameters		Value
Applicable communication scenarios		UMi, UMa, RMa [38.901] UMi-AV, UMa-AV, RMa-AV
Sensing transmitters and receivers properties	Rx/Tx Locations	Rx/Tx locations are selected among the TRPs and UEs locations in the corresponding communication scenarios. NOTE1: This may include aerial UEs for UMi-AV, UMa-AV, RMa-AV communication scenarios. In this case, other Rx/Tx properties (e.g. mobility) are also taken from the corresponding communication scenario.
Sensing target	LOS/NLOS	LOS and NLOS
	Outdoor/indoor	Outdoor
	3D mobility	Horizontal velocity: uniform distribution between 0 and 180km/h, if horizontal velocity is not fixed to 0. Vertical velocity: 0km/h, optional {20, 40} km/h NOTE2: 3D mobility can be horizontal only or vertical only or a combination for each sensing target ~~FFS: time-varying velocity.~~ NOTE 3: time-varying velocity may be considered for future evaluations.
	3D distribution	Horizontal plane: Option A: N targets uniformly distributed within one cell. Option B: N targets uniformly distributed per cell. Option C: N targets uniformly distributed within an area not necessarily determined by cell boundaries. ~~FFS: Value of~~ N, ~~defined area, and other distributions~~ N = {1, 2, 3, 4, 5} NOTE4: N=0 may be considered for the evaluation of false alarm Vertical plane: Option A: Uniform between 1.5m and 300m. Option B: Fixed height value chosen from {25, 50, 100, 200, 300} m assuming vertical velocity is equal to 0. ~~FFS Other options are not precluded.~~ ~~NOTE5: target(s) are outside the minimum distance to the Tx/Rx~~
	Orientation	Random in horizontal domain
	Physical characteristics (e.g., size)	Size: l Option 1: 1.6m x 1.5m x 0.7m l Option 2: 0.3m x 0.4m x 0.2m ~~FFS: Material(s), Structure, Other size(s)~~
Minimum 3D distances between pairs of Tx/Rx and sensing target		~~Option B~~: Min distances based on min. TRP/UE distances defined in TR36.777 as a starting point. NOTE5: the sensing target is assumed in the far field of sensing Tx/Rx ~~Option C: Min. distance is larger than the min. far-field distance of the sensing Tx/Rx~~
Minimum 3D distance between sensing targets		Option 1: At least larger than the physical size of a target Option 2: 10 meters
[Unintended/Environment objects, e.g., types, characteristics, mobility, distribution, etc.]		FFS

NOTE: A percentage of TRPs/UEs that have sensing capabilities may be considered for future evaluations.

R1-2410338 FL Summary #2 on ISAC Deployment Scenarios Moderator (AT&T)

From Thursday session

Agreement

For Automotive sensing target scenarios, the following table is agreed for deployment scenario parameters/values using the agreements from RAN1#118-bis as a baseline:

The detailed scenario description in this clause can be used for channel model calibration.

ISAC-Automotive

Details on ISAC-Automotive scenarios are listed in Table x.

Table x. Evaluation parameters for Automotive sensing scenarios

Parameters		Values
Applicable communication scenarios		Highway, Urban Grid. NOTE1
Sensing transmitters and receivers properties		Rx/Tx locations are selected among the TRPs and UEs (e.g., VRU, vehicle, RSU-type UEs) locations in the corresponding communication scenario. NOTE2 ~~FFS:~~ Additional option: ISD between TRPs of Urban Grid is 250m
Sensing target	LOS/NLOS	LOS and NLOS (including NLOSv)
	Outdoor/indoor	Outdoor
	Mobility (horizontal plane only)	Based on TR37.885 mobility for urban grid or highway scenario
	Distribution (horizontal)	Based on dropping in TR37.885 per urban grid or highway communication scenario
	Orientation	Lane direction in horizontal plane
	Physical characteristics (e.g., size)	Type 1/2 (passenger vehicle) Type 3 (truck/bus) Vehicle type distribution per TR 37.885 as a starting point ~~FFS:~~ ~~Other sizes, additional distributions, and vehicle types, e.g. one new type of e-scooter/motorcycle/bike~~
Minimum 3D distances between pairs of Tx/Rx and sensing target		~~Option 1:~~ Min distances based on min. TRP/UE distances defined in TR37.885 as a starting point. ~~Option 2: Min. distance is larger than the min. far-field distance of the sensing Tx/Rx~~ NOTE3: the sensing target is assumed in the far field of sensing Tx/Rx
Minimum 3D distance between sensing targets		Option 1: At least larger than the physical size of a sensing target Option 2: Fixed value, [10] m. ~~value of x is FFS~~
Environment Objects, e.g., types, characteristics, mobility, distribution, etc.		EO Type 2 for Urban Grid - ~~FFS: details, e.g.~~ up to 4 walls modelled as EO type 2, per building of size [413m x 230m x 20m]. FFS: number of buildings, how many walls are modelled, additional building sizes, etc.

NOTE1: Calibration for UMi, Uma, RMa is not performed for the automotive scenario, but UMi, Uma, RMa can be considered for future evaluations of the automotive sensing target scenarios. Calibration for UMi, Uma, RMa is expected to be performed for another sensing scenario.

NOTE2: A percentage of TRPs/UEs that have sensing capabilities may be considered for future evaluations.

Agreement

For Human (indoor and outdoor) sensing target scenarios, the following table is agreed for deployment scenario parameters/values using the agreements from RAN1#118-bis as a baseline:

The detailed scenario description in this clause can be used for channel model calibration.

ISAC-Human

Details on ISAC-Human scenarios are listed in Table x.

Table x. Evaluation parameters for Human (indoor and outdoor) sensing scenarios

Parameters		Indoor Values	Outdoor Values
Applicable communication scenarios NOTE1		Indoor office, indoor factory [TR38.901] Indoor room [TR38.808]	UMi, Uma, RMa [TR38.901]
Sensing transmitters and receivers properties	Rx/Tx Locations NOTE 2	Rx/Tx locations are selected among the TRPs and UE locations in the corresponding communication scenario	Rx/Tx locations are selected among the TRPs and UE locations in the corresponding communication scenario
Sensing transmitters and receivers properties	Rx/Tx Mobility for UEs	Option 1: 0km/h Option 2: 3km/h Option 3: Uniform distribution between 0km/h and 3km/hr	Option 1: 0km/h Option 2: 3km/h Option 3: Uniform distribution between 0km/h and 10km/hr
Sensing target	LOS/NLOS	LOS and NLOS	LOS and NLOS
	Outdoor/indoor	Indoor	Outdoor
	3D mobility	Option 1: 0km/h Option 2: 3km/h Option 3: Uniform distribution between 0km/h and 3km/hr (horizontal plane with random direction straight-line trajectory)	Option 1: 0km/h Option 2: 3km/h Option 3: Uniform distribution between 0km/h and 10km/hr (horizontal plane with random direction straight-line trajectory)
	3D distribution	N targets uniformly distributed over the horizontal area of the convex hull of the TRP deployment ~~FFS: Value of N~~ NOTE1: N=0 may be considered for the evaluation of false alarm	Option A: N targets uniformly distributed within one cell. Option B: N targets uniformly distributed per cell. Option C: N targets uniformly distributed within an area not necessarily determined by cell boundaries. ~~Uniform in horizontal plane~~ NOTE1: N=0 may be considered for the evaluation of false alarm
	Orientation	Random over the horizontal area	Random over the horizontal area
	Physical characteristics (e.g., size)	Size (Length x Width x Height): - Child: 0.2m x 0.3m x 1m - Adult Pedestrian: 0.5m x 0.5m x 1.75m	Size (Length x Width x Height): - Child: 0.2m x 0.3m x 1m - Adult Pedestrian: 0.5m x 0.5m x 1.75m
Minimum 3D distances between pairs of Tx/Rx and sensing target		~~Option 1: Min. distance is larger than the min. far-field distance of the sensing Tx/Rx~~ ~~Option 2:~~ Min distances defined in TR 38.901 and TR36.843 and TR38.859as a starting point NOTE2: the sensing target is assumed in the far field of sensing Tx/Rx	~~Option 1: Min. distance is larger than the min. far-field distance of the sensing Tx/Rx~~ ~~Option 2:~~ Min distances defined in TR 38.901 and TR36.843 and TR38.859 as a starting point NOTE3: the sensing target is assumed in the far field of sensing Tx/Rx
Minimum 3D distance between sensing targets		Option 1: At least larger than the physical size of a sensing target Option 2: Fixed value, [x] m. value of x is FFS	Option 1: At least larger than the physical size of a sensing target Option 2: Fixed value, [x] m. value of x is FFS
Environment Objects, e.g., types, characteristics, mobility, distribution, etc.		FFS, based on outcome for AI 9.7.2	FFS, based on outcome for AI 9.7.2

NOTE2: A percentage of TRPs/UEs that have sensing capabilities may be considered for future evaluations.

Agreement

For AGV sensing target scenarios, the following table is agreed for deployment scenario parameters/values using the agreements from RAN1#118-bis as a baseline:

The detailed scenario description in this clause can be used for channel model calibration.

ISAC-AGV

Details on ISAC-AGV are listed in Table x.

Table x. Evaluation parameters for Automated Guided Vehicles

Parameters		Value
Applicable communication scenarios NOTE1		InF (TR38.901 including Table 7.8-7)
Sensing transmitters and receivers properties NOTE2		Rx/Tx location are selected among the TRPs and UEs location in the corresponding communication scenario Rx/Tx Mobility for UEs - Option 1: 0 km/h - Option 2: 3km/h - Option 3: Uniform distribution between 0km/h and 3km/h
Sensing target	LOS/NLOS	LOS and NLOS
	Outdoor/indoor	Indoor
	3D mobility	Horizontal velocity with random straight-line trajectory - Option 1: Uniform distribution in the range of up to 30 km/h - Option 2: Fixed velocities [3, 10] km/h
	3D distribution	Option A: Uniformly distributed in the convex hull of the horizontal BS deployment Option B: Uniformly distributed in horizontal plane
	Orientation	Horizontal plane only
	Physical characteristics (e.g., size)	Size (L x W x H) - Option 1: 0.5m x 1.0m x 0.5m - Option 2: 1.5 m x 3.0m x 1.5 m - FFS: Material, Additional sizes, and AGV size distribution
Minimum 3D distances between pairs of Tx/Rx and sensing target		~~Option 1: Min. distance is larger than the min. far-field distance of the sensing Tx/Rx from the sensing target~~ ~~Option 2:~~ Min distances based on min. TRP/UE distances defined in TR38.901 NOTE: the sensing target is assumed in the far field of sensing Tx/Rx
Minimum 3D distance between sensing targets		Option A: At least larger than the physical size of a target Option B: Fixed value, [x] m. value of x is FFS
Environment objects, e.g., types, characteristics, mobility, distribution, etc.		FFS

NOTE1: For the AGV sensing targets, additional communication scenarios can be considered for future evaluations.

NOTE2: A percentage of TRPs/UEs that have sensing capabilities may be considered for future evaluations.

NOTE3: RAN1 can further discuss narrowing down the number of sub-scenarios of InF

Agreement

For Objects creating hazards sensing target scenarios, the following table is agreed for deployment scenario parameters/values using the agreements from RAN1#118-bis as a baseline:

The detailed scenario description in this clause can be used for channel model calibration.

ISAC-Hazards

Details on ISAC-Hazards are listed in Table x.

Table x. Evaluation parameters for objects creating hazards

Parameters		Value
Applicable communication scenarios NOTE1		Highway, Urban grid, HST (High Speed Train)
Sensing transmitters and receivers properties NOTE2	Rx/Tx Locations	Rx/Tx locations are selected among the TRPs and UEs (e.g., VRU, vehicle, RSU-type UEs) locations in the corresponding communication scenarios. ~~FFS:~~ ~~Option 2~~ Additional option ISD between TRPs of Urban Grid is 250 m
Sensing target	LOS/NLOS	LOS and NLOS
	Outdoor/indoor	Outdoor
	3D mobility	Horizontal velocity: up to [10] km/h for humans and animals FFS: Additional velocities, trajectory
	3D distribution	Uniformly distributed in horizontal plane
	Orientation	Random distribution in horizontal plane
	Physical characteristics (e.g., size)	For human/pedestrians: Child: 0.2m x 0.3m x 1m Adult: 0.5m x 0.5m x 1.75m For animals: Size: 1.5m x 0.5m x 1 m ~~FFS: other types/sizes of targets may be considered for future evaluations~~
Minimum 3D distances between pairs of Tx/Rx and sensing target		~~Option 1:~~ Min. distance is ~~larger than the min. far-field distance of the sensing Tx/Rx from the sensing target~~ ~~Option 2:~~ based on min TRP/UE distances defined in TR37.885 and TR38.802 and TR36.843 and TR38.859 NOTE: the sensing target is assumed in the far field of sensing Tx/Rx
Minimum 3D distance between sensing targets		Option 1: At least larger than the physical size of a sensing target Option 2: Fixed value, [10] m. ~~value of x is FFS~~
Environment objects, e.g., types, characteristics, mobility, distribution, etc.		EO Type 2 for Urban Grid - ~~FFS: details, e.g.~~ up to 4 walls modelled as EO type 2, per building of size [413m x 230m x 20m]. FFS: number of buildings, how many walls are modelled, additional building sizes, etc.

NOTE1: For the objects creating hazards sensing targets, additional communication scenarios can be considered for future evaluations.

NOTE2: A percentage of TRPs/UEs that have sensing capabilities may be considered for future evaluations.

[Post-119-ISAC-01] – Jerome (AT&T)

Email discussion on simulation assumptions for channel model calibration, from January 8^th-17^th:

Companies are encouraged to provide initial channel model calibration assumptions, parameters, and values
Jerome to collect inputs, provide potential consolidated tables, proposals for consideration by January 17^th

Decision: The discussions are to be carried over to RAN1#120.

9.7.22 ISAC channel modelling

R1-2409394 Channel modelling for ISAC Huawei, HiSilicon

R1-2409472 Discussion on ISAC channel modeling EURECOM

R1-2409524 Discussion on channel modeling methodology for ISAC CMCC,BUPT,SEU, PML

R1-2409609 Discussion on ISAC channel modelling Samsung

R1-2409647 Discussion on ISAC channel modeling Spreadtrum, UNISOC

R1-2409693 Views on Rel-19 ISAC channel modelling vivo, BUPT

R1-2409718 Discussion on ISAC channel modelling TOYOTA InfoTechnology Center

R1-2410832 Discussion on ISAC channel modeling Intel Corporation (rev of R1-2410671, rev of R1-2409740)

R1-2409767 Discussion on ISAC channel modeling Nokia, Nokia Shanghai Bell

R1-2409777 Channel modeling for integrated sensing and communication with NR NVIDIA

R1-2410739 Discussion on ISAC channel modelling Apple (rev of R1-2409818)

R1-2409837 Discussion on ISAC channel modelling LG Electronics

R1-2409847 Discussion on ISAC channel modeling InterDigital, Inc.

R1-2410668 Discussion on ISAC channel model Xiaomi, BJTU, BUPT (rev of R1-2409908)

R1-2409953 Discussion on ISAC channel modelling CATT, CICTCI

R1-2409977 Discussions on ISAC Channel Modelling Lekha Wireless Solutions

R1-2410659 ISAC Channel Modeling and Measurement Validation BUPT, CMCC, VIVO (rev of R1-2409992)

R1-2410007 Discussion on ISAC channel modelling China Telecom

R1-2410098 Study on ISAC channel modelling OPPO

R1-2410126 Discussion on ISAC Channel Modelling Ericsson

R1-2410136 Discussion on ISAC channel modeling NIST

R1-2410163 ISAC channel modelling Tejas Networks Limited

R1-2410235 Views on Channel Modelling for ISAC Sony

R1-2410321 Discussion on Channel Modelling for ISAC Lenovo

R1-2410333 Discussions on ISAC Channel Modeling AT&T

R1-2410370 Considerations on ISAC channel modelling CAICT

R1-2410401 Discussion on ISAC channel modeling NTT DOCOMO, INC.

R1-2410648 Discussion on channel modelling for ISAC ZTE Corporation, Sanechips (rev of R1-2410448)

R1-2410660 Discussion on ISAC channel modelling Qualcomm Incorporated (rev of R1-2410490)

R1-2410525 Discussion on ISAC channel modelling MediaTek Inc.

R1-2410011 Summary #1 on ISAC channel modelling Moderator (Xiaomi)

From Tuesday session

Agreement

Bistatic RCS values for a scattering point of a target are obtained by fixing an incident direction in LCS of target and varying the scattered directions in LCS of target; then changing to other incident direction.

R1-2410012 Summary #2 on ISAC channel modelling Moderator (Xiaomi)

From Wednesday session

Agreement

To generate indirect paths of NLOS ray + NLOS ray in the target channel

Option 0 is recommended, i.e., ray level full convolution between Tx-target link and target-Rx link for radio propagation Case 1/2/3/4
Option 3 to generate a reduced number of indirect paths of NLOS ray + NLOS ray is recommended, i.e., ray level 1-by-1 random coupling between Tx-target link and target-Rx link is supported for radio propagation Case 1/2/3/4

If number of rays in the two links are different, e.g., M1, M2 respectively for link 1 and link 2,

If M1<M2, randomly M1 rays are selected in link 2, otherwise randomly M2 rays are selected in link 1

Other methods are up to company choice for complexity reduction
Both option 0 and 3 will be calibrated independently. Company should report which option is used in calibration

The power threshold for path dropping is X=[-25] dB

X is relative to the strongest indirect path in the target channel

FFS: further power normalization of target channel is performed after path dropping,
Note: power normalization when target channel and background channel are combined can be discussed separately
FFS The set of remaining indirect paths can be updated during movement of Tx, target or Rx

Agreement

The following RCS models are supported when human is modelled with single scattering point for monostatic, where different RCS values and/or models can be supported for human due to different size, shape, frequency, etc.

Model 1

B1=0 dB
A is mean RCS value
B2 is modelled using log-normal distribution

Model 2

B1 have dependency on incident/scattered angles, with further down-selection among the alternatives below:

§ Alt 1: formulated similar as the antenna radiation power pattern in 38.901

§ Alt 2: a function

§ Alt 3: Lookup table

B2 is modelled using log-normal distribution
FFS RCS component A

FFS: conditions for using which model

Agreement

The following RCS model is supported when vehicle is modelled with single scattering point for monostatic, where different RCS values can be supported for vehicle due to different size, shape, frequency, etc.

B1 have dependency on incident/scattered angles, with further down-selection among the alternatives below:

o Alt 1: formulated similar as the antenna radiation power pattern in 38.901

o Alt 2: a function

o Alt 3: Lookup table

B2 is modelled using log-normal distribution
FFS RCS component A

Agreement

When vehicle is modelled with multiple scattering points for monostatic, where different RCS values can be supported for vehicle due to different size, shape, frequency, etc.

the recommended five scattering points are located in front, left, back, right and roof side of the vehicle
the following RCS model is supported for each scattering point

B1 have dependency on incident/scattered angles, with further down-selection among the alternatives below:

Alt 1: formulated similar as the antenna radiation power pattern in 38.901
Alt 2: a function
Alt 3: Lookup table

B2 is modelled using log-normal distribution
FFS RCS component A

Agreement

EO type-1 (when modelled) is modelled in the same way as a sensing target in the ISAC channel model.

Agreement

If blockage/forward scattering between sensing targets is not considered, a propagation path from Tx to Rx interacting with more than one sensing targets is not modelled.
FFS whether/how blockage/forward scattering can be modelled in the target channel.

Agreement

Doppler for a target including both macro-Doppler and micro-Doppler can be modeled using a unified formula,

Where,

is the spherical unit vector at receiver for the link from Rx to the scattering point
is the spherical unit vector at transmitter for the link from Tx to the scattering point
is the spherical unit vector at the scattering point for the link from the scattering point to Rx
is the spherical unit vector at the scattering point for the link from the scattering point to Tx

Dual mobility model in 7.6.10, TR 38.901 is used as start point to model Doppler effect due to movement of stochastic clusters, i.e.,

is only applicable for indirect path
Support one term of for indirect path of LOS ray+NLOS ray, NLOS ray+LOS ray
Support two terms of for indirect path of NLOS ray+NLOS ray

Doppler is separately determined for each of the multiple scattering points of a target
can include macro-Doppler and/or micro-Doppler motion,
FFS: maximum speed of moving scatterers
FFS: ratio of moving scatterers among all scatterers

R1-2410013 Summary #3 on ISAC channel modelling Moderator (Xiaomi)

From Thursday session

Agreement

The following options are supported to generate the combined ISAC channel

Option 1: The ISAC channel of a pair of sensing Tx/Rx is obtained by summing the target channel(s) and background channel, i.e., power normalization is not performed.
Option 2: As an additional modelling component, power normalization is performed when summing the target channel(s) and background channel, to keep the same/similar channel power as the background channel without target. Down select between

Alt 1: Power normalization on both target channel and background channel
Alt 2: Power normalization on background channel only
Alt 3: the target channel of a target will replace one cluster in the background channel

FFS Blockage is modelled for the background channel due to sensing target and/or EO type-2
FFS condition to select option, e.g. depending on scenario, sensing mode, number of target/EO type-2

Agreement

To model the polarization matrix of a direct/indirect path at a scattering point of an object other than EO type-2, the polarization matrix of the scattering point, i.e., is modelled by and initial random phases , i.e.,

· The initial random phase is [uniformly distributed within

· FFS correlation between

· FFS specular reflection

· FFS: CPM normalization

The following options are considered for further study, down select one option from the following

Option 1: , is generated for path i, where is XPR ratio

is randomly generated by log-normal distribution. FFS mean/variance of the distribution

Option 2: , are variables generated for path i
Option 3: are variables generated for path i

defined in LCS

Option 4: , is generated for path i

Agreement

The finite size of the EO type-2 affects identification of specular reflection point. In the target channel, EO type-2 is modelled only if the specular reflection point is in the area of the EO type-2.

Agreement

Component B2 of RCS is upper bounded by kσ dB for the log-normal distribution, where σ is the standard deviation of B2 in dB. FFS the value of k.

Agreement

When the EO type-2 is modelled in the target channel, down select between the following options to determine the LOS condition of the Tx-target link and target-Rx link

Option A: If type-2 EO is in the LOS ray of one link, the link is determined as NLOS condition, and otherwise use the LOS probability equation to determine the LOS/NLOS condition

FFS changes to the LOS probability defined in existing TRs
FFS details on blockage by EO type-2

Option B: Use the LOS probability equation to determine the LOS/NLOS condition of one link, and then the impacts of type-2 EO is modeled by a blockage model.

Final summary in R1-2410014.

RAN1#120

9.7 Study on channel modelling for Integrated Sensing And Communication (ISAC) for NR

Please refer to RP-242348 for detailed scope of the SI.

R1-2501548 Session notes for 9.7 (Study on channel modelling for Integrated Sensing And Communication for NR) Ad-Hoc Chair (Huawei)

Friday decision: The session notes are endorsed and contents reflected below.

[120-R19-ISAC] – Yingyang (xiaomi)

Email discussion on Rel-19 ISAC channel model

- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2500998 Draft CR for TR 38.901 to introduce channel model for ISAC Xiaomi, AT&T

Revised in

R1-2501640 Draft CR for TR 38.901 to introduce channel model for ISAC Moderator (Xiaomi)

R1-2501641 Summary on discussions on CR to 38.901 on ISAC channel modeling Moderator (Xiaomi)

From Friday session

[Post-120-ISAC-01] – Yingyang (Xiaomi)

Email discussion on values/pattern of A*B1 of RCS for target for monostatic sensing, from March 3-7

Companies to provide values of the parameters (referring the example table in the agreement) on A*B1 for vehicle, until March 5, targeting agreement on merged values by March 7.
Collect companies views on the possible extension of the agreement (except the example table) on A*B1 of RCS for vehicle to other target types with angle-dependent RCS until March 7, for potential agreement.

9.7.1 ISAC deployment scenarios

Please provide your inputs on calibrations is to this sub-agenda item.

R1-2500059 Email discussion summary on ISAC CM calibration assumptions Moderator (AT&T)

R1-2500071 Deployment scenarios for ISAC channel model Huawei, HiSilicon

R1-2500234 Discussion on ISAC deployment scenarios CATT, CICTCI

R1-2500266 Discussion on ISAC deployment scenarios China Telecom

R1-2500297 Discussion on ISAC deployment scenarios CMCC, China Southern Power Grid

R1-2500312 Discussion on ISAC scenario CALTTA

R1-2500360 Views on Rel-19 ISAC deployment scenarios vivo

R1-2500413 Discussion on ISAC deployment scenarios and requirements EURECOM

R1-2500417 Discussion on ISAC deployment scenarios Tiami Networks

R1-2500462 Discussion on ISAC deployment scenarios and calibration OPPO

R1-2500576 Discussion on ISAC deployment scenarios ZTE Corporation, Sanechips

R1-2500659 Discussion on ISAC deployment scenarios Sony

R1-2500679 Discussion on ISAC Deployment Scenarios Nokia, Nokia Shanghai Bell

R1-2500684 Discussion on ISAC deployment scenarios SK Telecom

R1-2500691 Deployment scenarios for integrated sensing and communication with NR NVIDIA

R1-2500742 Deployment scenarios and evaluation assumptions for ISAC channel model Xiaomi

R1-2500747 Discussion on ISAC deployment scenarios InterDigital, Inc.

R1-2500755 Discussion on ISAC Deployment Scenarios Ericsson

R1-2500796 Discussion on ISAC deployment scenarios Apple

R1-2500860 Discussion on ISAC deployment scenarios Samsung

R1-2500891 Considerations on ISCA deployment scenarios CAICT

R1-2501011 Discussion on ISAC deployment scenarios for Automotive Continental Automotive

R1-2501026 Discussion on ISAC deployment scenario MediaTek Inc.

R1-2501045 Discussion on ISAC deployment scenarios LG Electronics

R1-2501059 Discussion on ISAC deployment scenarios Lenovo

R1-2501081 ISAC channel model calibration and scenario parameters AT&T, FirstNet

R1-2501135 Discussion on ISAC channel calibration BUPT, CMCC

R1-2501166 Discussion on ISAC deployment scenarios Qualcomm Incorporated

R1-2501076 FL Summary #1 on ISAC Scenarios and Calibrations Moderator (AT&T)

R1-2501077 FL Summary #2 on ISAC Scenarios and Calibrations Moderator (AT&T)

From Wednesday session

Agreement

For ISAC channel modelling calibration, RAN1 considers both large-scale and full-scale calibration to include parameters and values for at least the following:

large scale parameters, where fast fading is not included
full-scale calibration parameters, which includes fast fading.

NOTE0: one part of calibration work does not include additional components and does not include spatial consistency

FFS: whether spatial consistency is specified as an additional component for ISAC CM

NOTE1: additional calibrations including spatial consistency can also be considered case by case for different scenarios.
NOTE2: Inclusion of EO in ISAC CM calibrations can also be considered case by case for different scenarios.

Agreement

Calibration of ISAC CM includes separate calibration of the target channel and of the background channel

· FFS: additional calibration for the combined channel (combination of target and background channel).

R1-2501078 FL Summary #3 on ISAC Scenarios and Calibrations Moderator (AT&T)

Presented in Thursday morning session.

R1-2501574 FL Summary #4 on ISAC Scenarios and Calibrations Moderator (AT&T)

From Thursday session

Agreement

For the purposes of large scale calibration for UAV sensing targets, the following calibration parameters are proposed below in Table x.

Table x. Simulation assumptions for large scale calibration for UAV sensing targets

Parameters	Values
Scenario	UMa-AV
Sensing mode	TRP monostatic, TRP-TRP bistatic, TRP-UE bistatic, UE-UE bistatic Note: further down-selection of the sensing modes for UAV sensing is not precluded
Sectorization	3 sectors per cell site: 30, 150 and 270 degrees
Carrier Frequency	FR1: 6 GHz FR2: 30 GHz
BS antenna configurations	Single dual-pol isotropic antenna
BS Tx power	FR1: 56dBm FR2: 41dBm
Bandwidth	FR1: 100MHz FR2: 400MHz
BS noise figure	FR1: 5dB FR2: 7dB
UT antenna configurations	(M,N,P,Mg,Ng;Mp,Np) = (1,1,2,1,1;1,1)
UT noise figure	FR1: 9dB FR2: 10dB
Sensing target distribution	1 target uniformly distributed (across multiple drops) within the center cell. Vertical distribution: Fixed height value of 200 m.
Component A of the RCS for each scattering point	a fixed value of A
Minimum 3D distances between pairs of Tx/Rx and sensing target	10 m
Wrapping Method	No wrapping method is used if interference is not modelled, otherwise geographical distance based wrapping
Metrics	Coupling loss (based on LOS pathloss) · FFS: how to select sensing Tx and Rx FFS: additional metrics, wideband SIR and SINR based on RSRP if interference is modelled.

Final summary in R1-2501607.

9.7.22 ISAC channel modelling

R1-2500072 Channel modelling for ISAC Huawei, HiSilicon

R1-2500179 Discussion on ISAC channel modeling Spreadtrum, UNISOC

R1-2500235 Discussion on ISAC channel modelling CATT, CICTCI

R1-2500267 Discussion on ISAC channel modelling China Telecom

R1-2500298 Discussion on channel modeling methodology for ISAC CMCC, BUPT, SEU, PML

R1-2500313 Discussion on ISAC channel modelling CALTTA

R1-2500361 Views on Rel-19 ISAC channel modelling vivo, BUPT

R1-2500414 Discussion on ISAC channel modeling EURECOM

R1-2500418 Discussion on ISAC Channel Modeling Tiami Networks

R1-2501363 Study on ISAC channel modelling OPPO (rev of R1-2500463)

R1-2500483 Discussion on ISAC channel modelling Tejas Network Limited

R1-2500577 Discussion on channel modelling for ISAC ZTE Corporation, Sanechips

R1-2501369 ISAC Channel Modeling and Measurement Validation BUPT, CMCC, VIVO (rev of R1-2500626)

R1-2500660 Discussion on Channel Modelling for ISAC Sony

R1-2500680 Discussion on ISAC channel modeling Nokia, Nokia Shanghai Bell

R1-2500681 Discussion on ISAC Channel Modeling NIST

R1-2500685 Discussion on ISAC channel modelling SK Telecom

R1-2500692 Channel modeling for integrated sensing and communication with NR NVIDIA

R1-2500743 Discussion on ISAC channel model Xiaomi, BJTU, BUPT

R1-2501368 Discussion on ISAC channel modeling InterDigital, Inc. (rev of R1-2500748 Discussion on ISAC)

R1-2500756 Discussion on ISAC Channel Modelling Ericsson

R1-2500797 Discussion on ISAC channel modelling Apple

R1-2500861 Discussion on ISAC channel modelling Samsung

R1-2500892 Considerations on ISAC channel modelling CAICT

R1-2500979 Discussion on ISAC Channel Modelling Panasonic

R1-2501027 Discussion on ISAC channel modelling MediaTek Inc.

R1-2501046 Discussion on ISAC channel modelling LG Electronics

R1-2501060 Discussion on Channel Modelling for ISAC Lenovo

R1-2501082 Discussions on ISAC Channel Modeling AT&T

R1-2501167 Discussion on ISAC channel modelling Qualcomm Incorporated

R1-2501212 Discussion on ISAC channel modeling NTT DOCOMO, INC.

R1-2500999 Summary #1 on ISAC channel modelling Moderator (Xiaomi)

From Tuesday session

Agreement

For bistatic/monostatic RCS

· RCS values/pattern for a scattering point of a target for bistatic sensing is generated by A*B1*B2 (i.e., Option 3 from the agreement in RAN1 #118bis)

· RCS values/pattern obtained by setting the same incident/scattered angle in the RCS model for bistatic sensing should be aligned with RCS for monostatic sensing

Agreement

RCS model and application in ISAC channel generation

To define the RCS model (RCS=A*B1*B2) for a scattering point of a target, when the target type is vehicle, large size UAV, human with RCS model 2, AGV

The values/pattern of the product of component A and B1, i.e., A*B1 is given per target type, expressed in dBsm scale
Component A is expressed in dBsm scale. B1 is dependent on A*B1 and value of component A.

A is equal to a single value per target type

FFS: this allows different values for the same target type with different size, if needed
FFS: this allows different values for monostatic and bistatic sensing, if needed

Component B2 follows log-normal distribution. The mean and variance used to characterize satisfied a fixed relation .

In the procedure of generating ISAC target channel, B1*B2 is applied after coupling of rays for a STX-SPST link and the corresponding SPST-SRX link before path dropping
In the procedure of generating ISAC target channel, the following power scaling factor is applied in the last step in target channel generation (i.e., step 14 in the running CR).

Where,

o is pathloss between Tx and SPST, where is the distance between Tx and SPST

o is pathloss between Rx and SPST, where is the distance between SPST and Rx

o is the value of RCS component A

o are shadow fading respectively generated for the Tx- SPST link and SPST -Rx link referring to step 4 in section 7.5, TR 38.901

o Note: for monostatic sensing,

Agreement

RCS upper bound: k equals to 3 is adopted to derive the upper bound of RCS component B2, kσ, where σ is the standard deviation of B2 in dB.

Agreement

For reducing options for reference TRs: for sensing scenario UMi, UMa, RMa, InH, InF, UMi-AV, UMa-AV, and RMa-AV, the reference TR to generate a TRP-TRP channel is:

TRP-TRP link of scenario UMi, UMa, InH, and InF following the option based on TR 38.901 defined in section A.3 of TR 38.858

For InF, h_UE is changed to the same height as the BS

TRP-UE link of scenario RMa defined in section 7 of TR 38.901 by setting h_UE=35m
FFS: whether to add very low power clusters

R1-2501000 Summary #2 on ISAC channel modelling Moderator (Xiaomi)

From Wednesday session

Agreement

For vehicle with single/multiple scattering points:

For mono-static, the RCS=A*B=A*B1*B2 for a scattering point of a vehicle is generated by

The values/pattern A*B1, i.e., is deterministic based on incident/scattered angles

Where,

For example, in case of vehicle with multiple scattering points:

							Applicable Range of	Applicable Range of
Left	[ ]	[ ]	[ ]	[ ]	[ ]	[ ]	[ ]	[ ]
Back	[ ]	[ ]	[ ]	[ ]	[ ]	[ ]	[ ]	[ ]
Right	[ ]	[ ]	[ ]	[ ]	[ ]	[ ]	[ ]	[ ]
Front	[ ]	[ ]	[ ]	[ ]	[ ]	[ ]	[ ]	[ ]
Roof	[ ]	[ ]	[ ]	[ ]	[ ]	[ ]	[ ]	[ ]

· Note: the applicable angular range is 360 degrees per row in horizontal domain in case of vehicle with multiple scattering points, and the applicable angular range is < 360 degrees per row in horizontal domain in case of vehicle with a single scattering point.

o FFS: angular continuity

Working assumption

For modelling background channel for monostatic sensing:

Solution A: (previous Option 1)

drop N reference point(s) following certain distribution, and then the background channel is generated based on the channel generated as in existing TR between the real Tx and the reference point for a scenario.

The distance between Tx and the reference point, and the height of the reference point follow Gamma distribution,

FFS: value of N (N<4)

FFS: whether to add additional very low power clusters
FFS: any update to parameters e.g. angular distribution and delay spread

Agreement

The existing spatial consistency model in TR 38.901 is reused to model correlation of links between one TRP and different STs/UEs.

Agreement

Spatial consistency is not modelled at least for the following links

Case 1: the links from/to two non-co-located TRPs

Link TRP1-X and link TRP2-X, where node X can be a target, a UE or another TRP
Link TRP1-X and link TRP2-Y, where node X, Y can be a target, a UE or another TRP

Case 2: the two links with different LOS/NLOS condition
Case 3: background channel for monostatic vs. any link (Tx-ST, ST-Rx, background channel) for bistatic

R1-2501001 Summary #3 on ISAC channel modelling Moderator (Xiaomi)

From Thursday session

Agreement

For sensing scenario UMi, UMa, RMa, InH, InF, UMi-AV, UMa-AV, and RMa-AV, the reference TR to generate a UE-UE channel is

· UE-UE link of scenario UMi, UMa, InH, and InF following the option based on TR 38.901 defined in section A.3 of TR 38.858

· TRP-UE link of scenario RMa defined in section 7 of TR 38.901 by setting h_BS =1.5m

· FFS: whether to add very low power clusters

Agreement

The reference TR to generate a TRP-UE channel is

TRP

normal UE

UMi, UMa, RMa, InH, InF, UMi-AV, UMa-AV, and RMa-AV

• Option 1: TRP-UE link of scenario UMi, UMa, RMa, InH, and InF in section 7 of TR 38.901

Highway and Urban grid

• Option 1: P2B link of scenario Highway and Urban grid in section 6 of TR 37.885

HST

• Option 1: TRP-UE link of scenario RMa in section 7 of TR 38.901 for FR1 and TRP-UE link of scenario UMa in section 7 of TR 38.901 for FR2

TRP

vehicle UE

Highway and Urban grid

Ÿ Option 1: V2B link of scenario Highway and Urban grid in section 6 of TR 37.885

UMi, UMa, and RMa

• Option 1: TRP-UE link of scenario UMi, UMa, and RMa in section 7 of TR 38.901

TRP

aerial UE

UMa-AV, UMi-AV, and RMa-AV

• Option 1:

- TRP-aerial UE link of scenario UMa-AV, UMi-AV, and RMa-AV in section Annex A and B of TR 36.777 for FR1

- FFS reuse the channel model of scenario UMa-AV, UMi-AV, and RMa-AV of FR1 for FR2

Agreement

For mono-static, the following values of component A, B2 are agreed for UAV of small size

Component A: -12.81 dBsm
Component B1: 0 dB (already agreed in RAN1#118bis)
Component B2:

standard deviation: 3.74 dB

Agreement

For mono-static, the following values of component A, B2 are agreed for RCS model 1 of human

Component A: -1.37 dBsm
Component B1: 0 dB (already agreed in RAN1#118bis)
Component B2:

standard deviation: 3.94 dB

Working assumption

Absolute delay model (referring to 7.6.9 in TR 38.901 as starting point) is a mandatory feature for both target channel and background channel for ISAC for UMi, UMa, InH, InF

· Related model referring to values from 7-24GHz study item

Agreement

When absolute delay model is configured, it applies to all NLOS clusters in each of Tx-target and target-Rx links and background channel.

· For bistatic sensing: Different values of are separately generated for the Tx-target link, target-Rx link and the background channel

· For monostatic sensing: the same value of is used for Tx-target link and target-Rx link, and a different value of is separately generated for the background channel

Agreement

To generate the LOS ray and NLOS clusters for the multiple scattering points, each scattering point is separately handled as if a different target with single scattering point.

Agreement

· The LOS condition between Tx/Rx and each of the multiple scattering points of a same target are individually generated

· The pathloss between Tx/Rx and each of the multiple scattering points of a same target are individually generated

Agreement

For a target with single/multiple scattering points, the 3D location of each scattering point is defined in the evaluation assumptions.

Agreement

Spatial consistency is needed to model correlation of the following links from ST-UT links and UT-UT links

· Case 5: links between same UT and two nodes X/Y, subjected to correlation distance, i.e., link UT1-X and link UT1-Y, where nodes X/Y can be target or UT

· Case 6: links between same target and two nodes X/Y, subjected to correlation distance, i.e., link target1-X and link target1-Y, where nodes X, Y are different UTs

· Case 7: link X1-Y1 and link X2-Y2, subjected to correlation distance, where X1, X2, Y1, Y2 are 4 different nodes

· FFS: Spatial consistency between multiple scattering points of the same target

Agreement

Correlation type is introduced for large scale parameter, cluster specific parameter and ray specific parameter of ST-UT links and UT-UT links

· Definition of link Correlated: parameters for any two links between STs/UTs are correlated, subjected to correlation distance.

Table 4: Correlation type for links between STs/UTs

Parameters	Correlation type
Delays	link Correlated
Cluster powers	link Correlated
AOA/ZOA/AOD/ZOD offset	link Correlated
AOA/ZOA/AOD/ZOD sign	link Correlated
Random coupling	link Correlated
XPR	link Correlated
Initial random phase	link Correlated
LOS/NLOS states	link Correlated
Blockage (Model A)	All-correlated
O2I penetration loss	All-correlated
Indoor distance	All-correlated
Indoor states	All-correlated

· Note: it is not precluded more parameters for spatial consistency can be discussed and added in the table

Agreement

If a target is modelled with multiple scattering points,

· The number of scattering points of the target is generated in the beginning of the simulation and kept unchanged in the whole simulation

· The number and locations of the scattering points of the target (if it is a vehicle) are common to each pair of sensing Tx/Rx

· RAN1 assumes no ray is scattered from one scattering point to another scattering point of the same target

· RCS values of the multiple scattering points are individually determined

Agreement

To model polarization matrix of a direct/indirect path i of a scattering point of a target

· in Rel-19 study item (e.g., UAV, human, vehicle, AGV), , , i.e.,

Where,

is XPR ratio is randomly generated by log-normal distribution per target type
The initial random phase is uniformly distributed within

FFS: spatial consistency of random phase when a scattering point moves
FFS: whether the base station rotation procedure in 38.901 can be reused to support rotation of the target

Agreement

For target channel

The power threshold for removing clusters in step 6 in section 7.5, TR 38.901, i.e., -25 dB is reused to generate Tx-target link and target-Rx link
The power threshold for path dropping after concatenation is relaxed to [X=-40] dB

For background channel

The power threshold for removing clusters in step 6 in section 7.5, TR 38.901, i.e., [-25 dB] is reused to generated the background channel

FFS: whether to add additional very low power clusters
FFS: The reference power for removing cluster is the min (max. Tx-target link cluster power, max. target-Rx link cluster power)

Agreement

If EO type-2 is modelled in an indirect path, only specular reflection is modeled for EO type-2

polarization of the indirect path is product of polarization matrix of the target-Rx link, the target, and the Tx-target link, i.e., CPM_tx,sp,rx= CPM_sp,rx . CPM_sp . CPM_tx,_sp

For the specular reflected ray generated by a EO type-2 in the Tx-target link or the target-Rx link (i.e., Tx-EO type-2-target, or target-EO type-2-Rx), CPM_tx,sp or CPM_sp,rx is the polarization matrix of EO type-2
To generate polarization matrix of EO type-2, the procedure in [R1-2409394, R1-2410648] is taken as starting point

FFS applicability if the surface of EO type-2 is tilted

Final summary in R1-2501002.

RAN1#120-bis

9.7 Study on channel modelling for Integrated Sensing And Communication (ISAC) for NR

Please refer to RP-242348 for detailed scope of the SI.

R1-2503113 Session notes for 9.7 (Study on channel modelling for Integrated Sensing And Communication for NR) Ad-Hoc Chair (Huawei)

Friday decision: The session notes are endorsed and contents reflected below.

[120bis-R19-ISAC] – Yingyang (xiaomi)

Email discussion on Rel-19 ISAC channel model

- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2502552 Draft CR for TR 38.901 to introduce channel model for ISAC Xiaomi, AT&T

Further revised in:

R1-2503072 Draft CR for TR 38.901 to introduce channel model for ISAC Xiaomi, AT&T

See [Post-120bis-ISAC-03].

From Friday session

[Post-120bis-ISAC-01] – Jerome (AT&T)

Email discussion for agreement on simulation assumptions for ISAC channel model calibrations, from April 21 to April 25.

- Moderator to provide parameter tables and calibration template for sensing targets based on agreements from RAN1#120-bis

[Post-120bis-ISAC-02] – Yingyang (Xiaomi)

Email discussion for agreement on parameter values for monostatic background channel, and values of parameters for monostatic RCS of UAV with large size and AGV, from April 21 to April 25.

[Post-120bis-ISAC-03] – Yingyang (Xiaomi)

Email discussion for endorsement of draft CR for TR38.901 update to introduce ISAC channel model, from April 28 to May 7 (

9.7.1 ISAC deployment scenarios

Please provide your inputs on calibrations is to this sub-agenda item.

R1-2501817 Views on Rel-19 ISAC deployment scenarios vivo

R1-2501839 Discussion on ISAC deployment scenarios and requirements EURECOM

R1-2501926 Discussion on ISAC deployment scenarios InterDigital, Inc.

R1-2501935 Deployment scenarios for integrated sensing and communication with NR NVIDIA

R1-2502002 Discussion on ISAC deployment scenarios CATT, CICTCI

R1-2502029 Discussion on ISAC deployment scenarios China Telecom

R1-2502051 Discussion on ISAC Deployment Scenarios Nokia, Nokia Shanghai Bell

R1-2502054 Discussion on ISAC deployment scenarios Tiami Networks

R1-2502062 Discussion on ISAC deployment scenarios ZTE Corporation, Sanechips

R1-2502067 Discussion on ISAC deployment scenarios Panasonic

R1-2502170 Discussion on ISAC channel model calibration CMCC, China Southern Power Grid

R1-2502207 Deployment scenarios for ISAC channel model Huawei, HiSilicon

R1-2502285 Discussion on ISAC channel model calibration OPPO

R1-2502325 Discussion on ISAC deployment scenarios Sony

R1-2502378 Discussion on ISAC deployment scenarios Samsung

R1-2502416 Discussion on ISAC deployment scenarios CALTTA

R1-2502418 Discussion on ISAC channel calibration BUPT, CMCC

R1-2502451 Deployment scenarios and evaluation assumptions for ISAC channel model Xiaomi

R1-2502465 Discussion on ISAC deployment scenarios TOYOTA InfoTechnology Center

R1-2502588 Discussion on ISAC deployment scenarios Lenovo

R1-2502623 Discussion on ISAC deployment scenarios Apple

R1-2502714 Discussion on ISAC deployment scenario MediaTek Inc.

R1-2502725 Discussion on ISAC Deployment Scenarios Ericsson

R1-2502820 Discussion on ISAC deployment scenarios LG Electronics

R1-2502849 Discussion on ISAC deployment scenarios Qualcomm Incorporated

R1-2502922 Considerations on ISCA deployment scenarios CAICT

R1-2502731 FL Summary #1 on ISAC Scenarios and Calibrations Moderator (AT&T)

R1-2502732 FL Summary #2 on ISAC Scenarios and Calibrations Moderator (AT&T)

From Wednesday session

Agreement

For the purposes of large scale calibration for UAV sensing targets, the following revised calibration parameters are proposed below in Table x. Note that the change bars are against the agreements from RAN1#120.

Table x. Simulation assumptions for large scale calibration for UAV sensing targets

Parameters	Values
Scenario	UMa-AV
Sensing mode	TRP monostatic, TRP-TRP bistatic, TRP-UE bistatic, UE-UE bistatic ~~Note: further down-selection of the sensing modes for UAV sensing is not precluded~~
Target type	UAV of small size (0.3m x 0.4m x 0.2m)
Sectorization	~~3 sectors per cell site: 30, 150 and 270 degrees~~ Single 360-degree sector can be assumed
Carrier Frequency	FR1: 6 GHz FR2: 30 GHz
BS antenna configurations	Single dual-pol isotropic antenna
BS Tx power	FR1: 56dBm FR2: 41dBm
Bandwidth	FR1: 100MHz FR2: 400MHz
BS noise figure	FR1: 5dB FR2: 7dB
UT antenna configurations	Single dual-pol isotropic antenna; (M,N,P,Mg,Ng;Mp,Np) = (1,1,2,1,1;1,1)
UT noise figure	FR1: 9dB FR2: 10dB
UT height	1.5m for terrestrial UTs,
UT Tx power	23dBm
UT Distribution	~~• 10 UTs uniformly distributed per sector in the center cell.~~ • The overall number of UTs is 30 uniformly distributed in the center cell. • All of the UTs are either terrestrial UTs or aerial UTs, all outdoors. • Vertical distribution of aerial UE: Fixed height value of 200 m. • FR1 is assumed for aerial UE.
Sensing target distribution	1 target uniformly distributed (across multiple drops) within the center cell. Vertical distribution: Fixed height value of 200 m.
Component A of the RCS for each scattering point	-12.81 dBsm ~~a fixed value of A~~
Minimum 3D distances between pairs of Tx/Rx and sensing target	10 m
Wrapping Method	No wrapping method is used if interference is not modelled, otherwise geographical distance based wrapping
Coupling loss for target channel	power scaling factor (pathloss, shadow fading, and RCS component A included):
Sensing Tx/Rx selection	Best N = 4 Tx-Rx pairs to be selected for the target. NOTE1: ~~TRP mono-static~~ ~~and~~ ~~TRP~~ ~~bistatic sensing scenarios~~: Based on the Tx-Rx pairs with the smallest power scaling factor of the target channel.
Metrics	Coupling loss for target channel ~~(based on LOS pathloss)~~ Coupling loss for background channel (in case of monostatic sensing, this is the coupling loss between Tx and one reference point) Note: CDFs can be separately generated for target channel, background channel l~~FFS: how to select sensing Tx and Rx~~ ~~FFS: additional metrics, wideband SIR and SINR based on RSRP if interference is modelled.~~

Agreement

For the purposes of full calibration for UAV sensing targets, the following calibration parameters are proposed below in Table x.

Table x. Simulation assumptions for full calibration for UAV sensing targets

Parameters	Values
Scenario	UMa-AV
Sensing mode	TRP monostatic, TRP-TRP bistatic, TRP-UE bistatic, UE-UE bistatic
Target type	UAV of small size (0.3m x 0.4m x 0.2m)
Sectorization	Single 360-degree sector can be assumed
Carrier Frequency	FR1: 6 GHz FR2: 30 GHz
BS antenna configurations	Single dual-pol isotropic antenna
BS Tx power	FR1: 56dBm FR2: 41dBm
Bandwidth	FR1: 100MHz FR2: 400MHz
BS noise figure	FR1: 5dB FR2: 7dB
UT antenna configurations	Single dual-pol isotropic antenna; (M,N,P,Mg,Ng;Mp,Np) = (1,1,2,1,1;1,1)
UT noise figure	FR1: 9dB FR2: 10dB
UT height	1.5m for terrestrial UTs
UT Tx power	23dBm
UT Distribution	· The overall number of UTs is 30 uniformly distributed in the center cell. · All of the UTs are either terrestrial UTs or aerial UTs, all outdoors. · Vertical distribution of aerial UE: Fixed height value of 200 m. · FR1 is assumed for aerial UE.
Sensing target distribution	1 target uniformly distributed (across multiple drops) within the center cell. Vertical distribution: Fixed height value of 200 m.
RCS for each scattering point	Component A: -12.81 dBsm Component B1: 0 dB Component B2: 3.74 dB for standard deviation The same values are used for monostatic RCS and bistatic RCS
Minimum 3D distances between pairs of Tx/Rx and sensing target	10 m
Wrapping Method	No wrapping method is used if interference is not modelled, otherwise geographical distance based wrapping
Fast fading model	TR 36.777 Annex B.1.3
(u, std) for XPR of target	Mean 13.75 dB, deviation 7.07 dB
The power threshold for path dropping after concatenation for target channel	FFS
The power threshold for removing clusters in step 6 in section 7.5, TR 38.901 for background channel	FFS
Coupling loss for target channel	By definition, need to consider all direct and indirect paths. The following parameters are included in the calculation: • power scaling factor (pathloss, shadow fading, and RCS component A included) • for small scale RCS B1/B2 and power of rays in Tx-target/target-Rx links (), Tx/Rx antenna pattern, 3 polarization matrixes, i.e.,

Sensing Tx/Rx selection	Best N = 4 Tx-Rx pairs to be selected for the target. NOTE1: Based on the Tx-Rx pairs with the smallest power scaling factor of the target channel.
Absolute delay	The model of UMa scenario defined in TR 38.901 7-24GHz channel modeling [ref] is reused for UMa-AV for all sensing modes.
Metrics	Coupling loss for target channel Coupling loss for background channel (in case of monostatic sensing, this is the linear sum of coupling losses between Tx/Rx and all reference points) Note: CDFs can be separately generated for target channel, background channel CDF of Delay Spread and Angle Spread (ASD, ZSD, ASA, ZSA). Definition of Delay Spread is similar to the definition of angle spread in Annex A of TR 25.996, Definition of Angle Spread can ref to Annex A of TR 25.996.

R1-2502733 FL Summary #3 on ISAC Scenarios and Calibrations Moderator (AT&T)

From Thursday session

Agreement

For the purposes of large scale calibrations for Automotive sensing targets, the following parameters are proposed below in Table x.

· FFS: which type of UE is used for UT in different sensing mode

· FFS: impact of spatial consistency, if any, in case of vehicle with 5 scattering points

· FFS: cell layout for ISD = 250 m

Table x. Simulation assumptions for large scale calibration for Automotive sensing targets

Parameters	Values
Scenario	For FR1: Urban Grid (ISD=500m, BS height=25m) Highway (ISD=1732m, BS height=35m) For FR2: Urban Grid (ISD=250m, BS height=25m) Highway (ISD=500m, BS height=35m)
Sensing mode	TRP monostatic, TRP-TRP bistatic, TRP-UE bistatic, UE-UE bistatic, UE monostatic
Target type	Vehicle type 2 [TR37.885]
Sectorization	Single 360-degree sector can be assumed
Carrier Frequency	FR1: 6 GHz FR2: 30 GHz
BS antenna configurations	Single dual-pol isotropic antenna
BS Tx power	FR1: 56dBm FR2: 41dBm
Bandwidth	FR1: 100MHz FR2: 400MHz
BS noise figure	FR1: 5dB FR2: 7dB
UT antenna configurations	Single dual-pol isotropic antenna, (M,N,P,Mg,Ng;Mp,Np) = (1,1,2,1,1;1,1)
UT noise figure	FR1: 9dB FR2: 10dB
UT height	1.5m for pedestrian type UE 5m for RSU type UE 1.6m for vehicle type UE
UT Tx power	23dBm
UT Distribution	Per TR37.885
Sensing target distribution	Per TR37.885: - Option A - Vehicle type distribution: 100% vehicle type 2. - Clustered dropping is not used. - Highway: one target uniformly distributed (across multiple drops) within the simulation region. Vehicle speed is 140 km/h in all the lanes as baseline. - Urban Grid: one target is uniformly distributed (across multiple drops) within the center road grid. Vehicle speed is 60 km/h in all the lanes as baseline. NOTE: vehicle is dropped with 5 scattering points (front/left/right/back/roof) and each point has one location, or vehicle is dropped with 1 scattering points
Component A of the RCS for each scattering point	-20dBsm
Minimum 3D distances between pairs of Tx/Rx and sensing target	10 m
Wrapping Method	As defined in urban grid/highway scenario
Coupling loss for target channel	Power scaling factor (pathloss, shadow fading, and RCS component A included)
Sensing Tx/Rx selection	Best N= Tx-Rx pairs to be selected for the target. For urban grid N = 4 For Highway N = 4 NOTE: Based on the Tx-Rx pair with the smallest power scaling factor of the target channel.
Metrics	Coupling loss for target channel Coupling loss for background channel (in case of monostatic sensing, this is the coupling loss between Tx and one reference point) Note: CDFs can be separately generated for target channel, background channel

Final summary in R1-2502734.

9.7.22 ISAC channel modelling

R1-2501818 Views on Rel-19 ISAC channel modelling vivo, BUPT

R1-2501840 Discussion on ISAC channel modeling EURECOM

R1-2501878 Discussion on ISAC channel modeling Spreadtrum, UNISOC

R1-2501927 Discussion on ISAC channel modeling InterDigital, Inc.

R1-2501933 Channel modelling for integrated sensing and communication with NR NVIDIA

R1-2502003 Discussion on ISAC channel modelling CATT, CICTCI

R1-2502030 Discussion on ISAC channel modelling China Telecom

R1-2502052 Discussion on ISAC channel modeling Nokia, Nokia Shanghai Bell

R1-2502055 Discussion on ISAC Channel Modeling Tiami Networks

R1-2502063 Joint views on mono-static background channel modeling ZTE Corporation, Sanechips, OPPO, BUPT, BJTU, CAICT, Xiaomi

R1-2502171 Discussion on channel modeling methodology for ISAC CMCC, BUPT, SEU, PML

R1-2502208 Channel modelling for ISAC Huawei, HiSilicon

R1-2503080 Study on ISAC channel modelling OPPO (rev of R1-2502286)

R1-2502326 Discussion on Channel Modelling for ISAC Sony

R1-2502379 Discussion on ISAC channel modelling Samsung

R1-2502417 Discussion on channel modelling for ISAC CALTTA, ZTE Corporation, Sanechips

R1-2502419 ISAC Channel Modeling and Measurement Validation BUPT, CMCC, VIVO

R1-2502452 Discussion on ISAC channel model Xiaomi, BJTU, BUPT

R1-2502466 Discussion on ISAC channel modelling TOYOTA InfoTechnology Center

R1-2502565 Discussion on ISAC channel modelling Tejas Network Limited

R1-2502572 Discussion on ISAC Channel Modeling NIST

R1-2502587 Discussion on Channel Modelling for ISAC Lenovo

R1-2502624 Discussion on ISAC channel modelling Apple

R1-2502715 Discussion on ISAC channel modelling MediaTek Inc.

R1-2502726 Discussion on ISAC Channel Modelling Ericsson

R1-2502736 Discussions on ISAC Channel Modeling AT&T

R1-2502776 Discussion on ISAC Channel Modelling NTT DOCOMO, INC.

R1-2502814 Discussion on ISAC channel modelling Panasonic

R1-2502821 Discussion on ISAC channel modelling LG Electronics

R1-2502850 Discussion on ISAC channel modelling Qualcomm Incorporated

R1-2502923 Considerations on ISAC channel modelling CAICT

R1-2502553 Summary #1 on ISAC channel modelling Moderator (Xiaomi)

From Tuesday session

Agreement

· In order to generate Tx-target link, target-Rx link and the background channel, the above table on reference TRs (excluding the already agreed part) is adopted for the mapping between reference TRs and a pair of nodes (STX, SRX, target).

o Note: continue discussion for updating the table with RSU type UE.

o FFS: the generation of background channel based on reference TRs is subject to the addition of low-energy clusters.

Case	Node 1	Node 2	Existing TRs as starting point
1	TRP	TRP	Highway · TRP-UE link of scenario RMa in section 7 of TR 38.901 by setting hUE=35m for FR1 · TRP-TRP link of scenario UMa following the option based on TR 38.901 defined in section A.3 of TR 38.858 Urban grid · TRP-TRP link of scenario UMa following the option based on TR 38.901 defined in section A.3 of TR 38.858 HST · TRP-UE link of scenario RMa in section 7 of TR 38.901 by setting hUE=35m for FR1 · TRP-TRP link of scenario UMa in section A.3 of TR 38.858 for FR2
4	TRP	aerial UE	UMa-AV, UMi-AV, and RMa-AV · Reuse the channel model of scenario UMa-AV, UMi-AV, and RMa-AV of FR1 for FR2
5	normal UE	normal UE	For pedestrian type UE: Highway and Urban grid · P2P link in section 6 of TR 37.885 HST · TRP-UE link of scenario RMa in section 7 of TR 38.901 for FR1, e.g., hBS=1.5m, UE-UE link of scenario UMa following the option based on TR 38.901 defined in section A.3 of TR 38.858 for FR2
6	normal UE	vehicle UE	UMi, UMa, RMa · UE-UE link of scenario UMi, UMa following the option based on TR 38.901 defined in section A.3 of TR 38.858 · TRP-UE link of scenario RMa defined in section 7 of TR 38.901 by setting h_BS =1.5m For pedestrian type UE: Highway and Urban grid · V2P link in section 6 of TR 37.885
7	normal UE	aerial UE	UMi-AV, UMa-AV, and RMa-AV · TRP-aerial UE link of UMi-AV in Annex A and B of TR 36.777 by setting h_BS =1.5m for FR1 o LOS probability is not reused, FFS new LOS probability o FFS pathloss model, shadowing fading · Working assumption: Reuse the channel model of scenario UMa-AV, UMi-AV, and RMa-AV of FR1 for FR2 o The corresponding parameter values in FR2 are used
8	vehicle UE	vehicle UE	Highway and Urban grid · V2V link of scenario Highway and Urban grid in section 6 of TR 37.885 UMi, UMa, and RMa · UE-UE link of scenario UMi, UMa following the option based on TR 38.901 defined in section A.3 of TR 38.858 · TRP-UE link of scenario RMa defined in section 7 of TR 38.901 by setting h_BS =1.5m
9	aerial UE	aerial UE	UMi-AV, UMa-AV, RMa-AV · TRP-aerial UE link of UMi-AV in Annex A and B of TR 36.777 by setting height of TRP equal to the height of the first aerial UE for FR1 o LOS probability is not reused, FFS new LOS probability o FFS pathloss model, shadowing fading, angular spread · Working assumption: Reuse the channel model of scenario UMa-AV, UMi-AV, and RMa-AV of FR1 for FR2 o The corresponding parameter values in FR2 are used

Agreement

To generate the parameters (in the steps before concatenation), the large-scale parameters and the small-scale parameters used to generate the Tx-target link are respectively the same as that of the target-Rx link for monostatic sensing, where departure angle on one link and arrival angle on the other link are reciprocal.

· FFS: whether this applies to initial phase

Agreement

Normalization on the product of three polarization matrixes of a direct/indirect path generated by stochastic cluster, i.e., CPM_tx,sp,rx= CPM_sp,rx . CPM_sp . CPM_tx,_sp is supported

· The scaling factor is

Agreement

Power normalization of target channel after path dropping of the target channel is not supported.

Agreement

On the monostatic RCS for human with RCS model 2

The monostatic RCS for a scattering point of the target is generated by

The values/pattern A*B1, i.e., is deterministic based on incident/scattered angles

Where,

FFS how many rows of the values/pattern A*B1 are defined for the target

Note: each row has a defined applicable range of and

Note: whether the RCS is elevation angle dependent or dependent on both elevation and horizontal angles can be separately discussed

Agreement

The following mean and standard deviation values of XPR of targets are agreed for monostatic sensing and bistatic sensing as follows:

· UAV: (13.75, 7.07) dB

· Human: (19.81, 4.25) dB

· Vehicle: (21.12, 6.88) dB

R1-2502554 Summary #2 on ISAC channel modelling Moderator (Xiaomi)

From Wednesday session

Agreement

When spatial consistency is enabled, the 1-by-1 random coupling generated by concatenation Option 3 is not updated per simulation drop even if Tx, target, Rx positions change during simulation.

Agreement

The following working assumption is confirmed.

Working assumption

Absolute delay model (referring to 7.6.9 in TR 38.901 as starting point) is a mandatory feature for both target channel and background channel for ISAC for UMi, UMa, InH, InF

· Related model referring to values from 7-24GHz study item

R1-2502555 Summary #3 on ISAC channel modelling Moderator (Xiaomi)

From Thursday session

Working assumption

For vehicle with single/multiple scattering points, the bistatic RCS is generated by

· The values/pattern of A*B1 of bistatic RCS is given by:

where

is applied to the within 0~180 degrees. k1= 6 and k2=~~[1 or 1.65]~~1.65. is the bistatic angle between the incident ray and scattering ray within the plane of incident direction () and scattering direction ().
The angles of () are the projections of the bisector angle on the vertical plane and the horizontal plane, respectively.

FFS: RCS value when is 180 degrees

The effect of forward scattering is -Inf in Rel-19
5 sets of parameters Applicable Range of and Applicable Range of are applicable as defined for the monostatic RCS of vehicle with single/multiple SPSTs
Continue study on a new formula for to resolve the issue of angular discontinuity.

The new formula should retain following property: the linear bistatic RCS for a vehicle with single scattering point is the sum of the bistatic RCS of the multiple scattering points of the vehicle
the following formula can be a reference for the study

Note: the working assumption agreed on Thursday was updated on Friday as follows: k1= 6 and k2=~~[1 or 1.65]~~1.65

R1-2502556 Summary #4 on ISAC channel modelling Moderator (Xiaomi)

From Friday session

Agreement

On background channel for mono-static sensing, the following details are provided:

reference points are dropped for one Tx, based on the Gamma distribution for distance and height of reference point.
The LOS AOD between Tx and the first reference point, which is denoted as AOD1, is generated based on uniform distribution .

The LOS AOD between Tx and the second reference point is AOD1 +
The LOS AOD between Tx and the third reference point is AOD1 +

The background channel is generated based on the channel generated as in existing TR between the real Tx and the reference point assuming NLOS condition.
The antenna field pattern and array orientation of reference point are set same as Tx.
Arrival angles for both azimuth and elevation and are set equal to departure angles.
The absolute delay model d3D and as agreed for bistatic sensing for the same sensing scenario applies. Down-select one option from the following:

Option 0: no scaling factor is applied to d3D.
Option 1: An offset is applied to d3D, i.e., d3D-c1.
Option 2: A scaling factor d_s is multiplied to d3D, i.e., d3D*d_s. d_s is a value within range [0, 1].
Note: The adjustment of absolute delay doesn’t impact the generation of NLOS clusters between the Tx and each reference point.

The mono-static background channel for the Tx would be sum of channels of the links between the Tx and all related reference points, which is

FFS: Doppler frequency in background channel for monostatic sensing.
The rays in a stochastic cluster with ZOA at BS less than D degree are dropped.

D=[90] for RMa.
D=[60] for UMa.
D=[50] for UMi.
Note: this threshold for ZOA is not applicable to other sensing scenarios.

Agreement

To generate the background channel, the power threshold (-25 dB) for removing clusters in step 6 in section 7.5, TR 38.901 is reused.

Agreement

The ISAC background channel can be generated between a sensing Tx and a sensing Rx or RP (relevant for monostatic case) via the following steps:

· Step 1: generate a first set of clusters/rays according to TR 38.901(or other related TRs)

· Step 2: generate a second set of NLOS clusters/rays according to TR 38.901 (or other related TRs), where the power of the second set of clusters/rays should be scaled down such that

is the power of the NLOS cluster with the strongest power from the first set.
is the power of the n-th cluster from the second set.
Where, N is the number of clusters, M is the number of rays within each cluster, value of G relates to power

o N=360, M=1, G = -25dB, no further change from 38.901, 36.777, 38.858 (i.e., utilizing the same DS, ASA, ASD, ZSA, ZSD, , as used for the first step).

The step 2 is an additional modeling component.

For email discussion

Proposal

The values of the parameters to generate background channel for TRP monostatic and UE monostatic sensing for each sensing scenario are provided in the following table.

· FFS parameter values for other scenarios (e.g. indoor factory).

· Email discussion/approval checking the values after April meeting, including validation for newly agreed parameters.

o The email discussion includes all scenarios, TRP monostatic and UE monostatic.

o The email discussion includes how to merge results provided by companies.

Scenario	Uma / Urban grid / Highway (FR2) / HST(FR2), (TRP monostatic)	UMi, (TRP monostatic)	Rma / Highway (FR1) / HST(FR1) . (TRP monostatic)	Indoor office (TRP monostatic)	Indoor office (UE monostatic)
Distribution of 2D distance between Tx and reference points 1	10.3370	6.1996	6.2025	4.236	4.3733
	0.1317	0.1558	0.0391	0.19255	0.4457
	68.7778	15.2697	1.2940	4.99	4.6302
Distribution of height of reference points	16.2253	12.0487	0.0007	1.3293	0.2974
	1.9218	2.3261	5.0146	0.1442	0.4103
	2.6142	0.0157	0.0522	13.19	2.9711

Agreement

For human as a sensing target with a single scattering point, the height of the scattering point is 1.5 m.

Agreement

In sensing scenario UMi, UMa, RMa, if the height of a scattering point of target is less than 1.5m, for pathloss calculation, down-selection one of the options below:

· Option 4: use in Table 7.4.1-1: Pathloss models in TR 38.901.

· Option 5: use h_UT 1.5 m for pathloss calculation.

Agreement

For sensing scenario UMi, UMa, RMa, UMi-AV, UMa-AV and RMa-AV, the height of a scattering point of a target is used to calculate the LOS probability and pathloss, regardless of the lower bound in the existing TRs that are referred to generate ISAC channel.

· FFS for the case where the height of a scattering point of target is less than 1.5m in sensing scenario UMi, UMa, RMa.

For email approval

[FL3] Proposal 4.2.1-1

On the monostatic RCS of UAV of large size,

· The values/pattern of component A*B1 are generated by the following parameters

							Applicable Range of	Applicable Range of
Left	90°	7.13°	90°	8.68°	7.43	14.30	[45°,135°]	[45°,135°]
Back	180°	10.09°	90°	11.43°	3.99	10.86	[45°,135°]	[135°,225°]
Right	270°	7.13°	90°	8.68°	7.43	14.30	[45°,135°]	[225°,315°]
Front	0°	14.19°	90°	16.53°	1.02	7.89	[45°,135°]	[-45°,45°]
Bottom	/	/	180°	4.93°	13.55	20.42	[135°,180°]	[0°,360°]
Roof	/	/	0°	4.93°	13.55	20.42	[0°,45°]	[0°,360°]

o When is in the range [0°,45° ] or [135°,180°],

· The standard deviation of component B2 is 2.50 dB

For email approval

[FL3] Proposal 4.2.3-1

On the monostatic RCS of AGV with single scattering point,

· The values/pattern of component A*B1 are generated by the following parameters

							Applicable Range of	Applicable Range of
Left	90°	19.45°	75°	19.45°	7.33	17.59	[30°,180°]	[45°,135°]
Back	180°	13.68°	90°	13.68°	11.01	21.27	[30°,180°]	[135°,225°]
Right	270°	19.45°	75°	19.45°	7.33	17.59	[30°,180°]	[225°,315°]
Front	0°	13.68°	90°	13.68°	13.02	23.29	[30°,180°]	[-45°,45°]
Roof	/	/	0°	16.57°	11.79	22.05	[0°,30°]	[0°,360°]

When is in the range [0°,30° ),

The standard deviation of component B2 is 2.51 dB

Final summary in R1-2503146.

RAN1#121

9.7 Study on channel modelling for Integrated Sensing And Communication (ISAC) for NR

Please refer to RP-242348 for detailed scope of the SI.

R1-2504895 Session notes for 9.7 (Study on channel modelling for Integrated Sensing And Communication for NR) Ad-Hoc Chair (Huawei)

Endorsed and incorporated below with update.

[121-R19-ISAC] Email discussion on Rel-19 ISAC channel model – Yingyang (xiaomi)

- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2504160 Draft CR for TR 38.901 to introduce channel model for ISAC Xiaomi, AT&T

[Post-121-ISAC-01] – Yingyang (Xiaomi)

Email discussion for endorsement of CR for TR38.901 update to introduce ISAC channel model, for submission to RAN plenary, from May 26 to May 30.

[Post-121-ISAC-02] – Jerome (AT&T)

Email discussion for collection of calibration results for the ISAC channel model, in 3 phases:

• For updating results for large scale calibration: Until August 1

• For full calibration results: Until August 21

• For additional feature calibration: Until August 21

• Companies can decide which option(s) to calibrate for those additional features with multiple options

• Rapporteur will provide separate excel templates for different options

9.7.1 ISAC deployment scenarios

Please provide your inputs on calibrations is to this sub-agenda item.

R1-2503247 Deployment scenarios for ISAC channel model Huawei, HiSilicon

R1-2503372 Views on Rel-19 ISAC deployment scenarios vivo

R1-2503445 Discussion on ISAC deployment scenarios and requirements EURECOM

R1-2503576 Discussion on ISAC deployment scenarios Samsung

R1-2503697 Discussion on ISAC deployment scenarios ZTE Corporation, Sanechips, CAICT

R1-2503752 Discussion on ISAC deployment scenarios InterDigital, Inc.

R1-2503760 Discussion on ISAC Deployment Scenarios SK Telecom

R1-2503803 Discussion on ISAC deployment scenarios CATT, CICTCI

R1-2503841 Discussion on full calibration of ISAC channel model CMCC

R1-2503858 Discussion on ISAC channel calibration BUPT, CMCC, X-Net

R1-2503892 Scenario and calibration discussion for ISAC CM Xiaomi

R1-2503954 Discussion on ISAC Deployment Scenarios Nokia, Nokia Shanghai Bell

R1-2503967 Discussion on ISAC deployment scenarios Tiami Networks

R1-2503992 Deployment scenarios for integrated sensing and communication with NR NVIDIA

R1-2504012 Discussion on ISAC Deployment Scenarios NIST

R1-2504053 Discussion on ISAC deployment scenarios China Telecom

R1-2504068 Remaining issues on ISAC deployment scenarios Sony

R1-2504126 Discussion on ISAC deployment scenarios CALTTA

R1-2504146 Discussion on calibration results ETRI

Late submission

R1-2504220 Discussion on ISAC channel model calibration OPPO

R1-2504239 Discussion on ISAC deployment scenarios Lenovo

R1-2504268 Discussion on ISAC deployment scenario MediaTek Inc.

R1-2504336 Discussion on ISAC deployment scenarios and Calibration Apple

R1-2504367 ISAC scenarios and 7-24GHz alignment AT&T, FirstNet

R1-2504404 Discussion on ISAC deployment scenarios Qualcomm Incorporated

R1-2504454 Discussion on ISAC Deployment Scenarios Ericsson

R1-2504539 Discussion of calibration for UAV sensing targets ITRI, Tron Future Tech Inc.

R1-2504566 Discussion on ISAC deployment scenarios LG Electronics

R1-2504363 FL Summary #1 on ISAC Scenarios and Calibrations Moderator (AT&T)

Agreement

Updates to Table 7.9.1-1: Evaluation parameters for UAV sensing scenarios are as follows:

Parameters

Value

Applicable communication scenarios

UMi, UMa, ~~Rma~~ RMa, SMa ~~[38.901]~~

UMi-AV, UMa-AV, RMa-AV [36.777]

[Unintended/Environment objects, e.g., types, characteristics, mobility, distribution, etc.]

Can be considered ~~for~~in future evaluations~~FFS~~

NOTE1: calibration for the UAV scenario is performed for UMa-AV scenario, but UMi-AV, RMa-AV, UMi, UMa, RMa, SMa can be considered for future evaluations of the UAV sensing target scenarios.

NOTE2: A percentage of TRPs/UEs that have sensing capabilities may be considered for future evaluations.

Conclusion

Channel model for ISAC for SMa scenario will not be fully studied in Rel-19.

Agreement

Updates to Table 7.9.1-2: Evaluation parameters for Automotive sensing scenarios are as follows:

Parameters

Values

Applicable communication scenarios

Highway, Urban Grid.

UMi, UMa, RMa, SMa. NOTE1

Environment Objects, e.g., types, characteristics, mobility, distribution, etc.

EO Type 2 for Urban Grid

- up to 4 walls modelled as EO type 2, per building of size 413m x 230m x 20m. ~~FFS: number of buildings, how many walls are modelled, additional~~ Additional building sizes, building heights, materials, etc., can be considered ~~for~~in future evaluations

NOTE1: calibration for the automotive scenario will be performed for Highway and Urban Grid scenarios.~~UMi, UmaUMa, RMa, SMa is not performed for the automotive scenario, but~~ UMi, ~~Uma~~UMa, RMa, SMa and related calibration parameters can be considered for future evaluations of the automotive sensing target scenarios. ~~Calibration for UMi, UmaUMa, RMa, SMa is expected to be performed for another sensing scenario.~~

NOTE2: A percentage of TRPs/UEs that have sensing capabilities may be considered for future evaluations.

Agreement

Updates to Table 7.9.1-3: Evaluation parameters for Human (indoor and outdoor) sensing scenarios as follows:

Parameters	Indoor Values	Outdoor Values
Applicable communication scenarios NOTE1	Indoor office, indoor factory ~~[TR38.901]~~ Indoor room [TR38.808]	UMi, ~~Uma~~UMa, RMa, SMa ~~[TR38.901]~~
Minimum 3D distance between sensing targets	Option 1: At least larger than the physical size of a sensing target Option 2: Fixed value, ~~[x]~~1 m. ~~value of x is FFS~~	Option 1: At least larger than the physical size of a sensing target Option 2: Fixed value, ~~[x]~~1 m. ~~value of x is FFS~~
Environment Objects, e.g., types, characteristics, mobility, distribution, etc.	Can be considered ~~for~~in future evaluations~~FFS, based on outcome for AI 9.7.2~~	Can be considered ~~for~~in future evaluations~~FFS, based on outcome for AI 9.7.2~~

Agreement

Updates to Table 7.9.1-4: Evaluation parameters for Automated Guided Vehicles sensing scenarios as follows:

Parameters		Value
Sensing Target	Physical characteristics (e.g., size)	Size (L x W x H) - Option 1: 0.5m x 1.0m x 0.5m - Option 2: 1.5 m x 3.0m x 1.5 m - ~~FFS:~~ Material, Additional sizes, and AGV size distribution can be considered ~~for~~in future evaluations
Minimum 3D distance between sensing targets		Option A: At least larger than the physical size of a target Option B: Fixed value, ~~[x]~~5 m. ~~value of x is FFS~~
Environment objects, e.g., types, characteristics, mobility, distribution, etc.		Can be considered ~~for~~in future evaluations~~FFS~~

Agreement

Updates to Table 7.9.1-5: Evaluation parameters for objects creating hazards sensing scenarios as follows:

Parameters		Value
Applicable communication scenarios NOTE1		Highway, Urban grid, HST (High Speed Train) UMi, UMa, RMa, SMa
Sensing Target	3D mobility	Horizontal velocity: up to [10] km/h for humans and animals ~~FFS:~~ Additional velocities, trajectory can be considered ~~for~~in future evaluations
Environment objects, e.g., types, characteristics, mobility, distribution, etc.		EO Type 2 for Urban Grid - up to 4 walls modelled as EO type 2, per building of size 413m x 230m x 20m. ~~FFS:~~ Additional building sizes, building heights, materials, etc., can be considered ~~for~~in future evaluations~~number of buildings, how many walls are modelled, additional building sizes, etc.~~

NOTE1: calibration for objects creating hazards scenario can be performed for Highway and Urban Grid scenarios. UMi, UMa, RMa, SMa and HST and related calibration parameters can be considered for future evaluations of the objects creating hazards scenarios.

Agreement

Updates to Table 7.9.7.1-3. Simulation assumptions for large scale calibration for Automotive sensing targets as follows:

Parameters	Values
Scenario	For FR1: Urban Grid (ISD=500m, BS height=25m) Highway (ISD=1732m, BS height=35m) For FR2: Urban Grid (ISD=250m, BS height=25m) Highway (ISD=500m, BS height=~~35m~~25m)
Component A of the RCS for each scattering point	11.25 dBsm~~20dBsm~~
Wrapping Method	No wrapping method is used if interference is not modelled, otherwise geographical distance based wrapping.~~As defined in urban grid/highway scenario~~

Agreement

Clarification for metrics for Simulation assumptions for full calibration sensing targets as follows:

The power threshold for path dropping after concatenation for target channel

[-40dB]

~~FFS: Other power thresholds.~~

The power threshold for removing clusters in step 6 in section 7.5, TR 38.901 for background channel

[-25dB]

~~FFS: Other power thresholds.~~

Metrics

Coupling loss for target channel

Coupling loss for background channel (in case of monostatic sensing, this is the linear sum of coupling losses between Tx/Rx and all reference points)

Note: CDFs can be separately generated for target channel, background channel

CDF of Delay Spread and Angle Spread (ASD, ZSD, ASA, ZSA)

For monostatic sensing mode : delay spread and angle spread of the background channel is calculated separately for each reference point ~~based on paths from all reference points~~.

Definition of Delay Spread is similar to the definition of angle spread in Annex A of TR 25.996,

Definition of Angle Spread can ref to Annex A of TR 25.996.

Agreement

Updates to Table 7.9.7.2-2: Simulation assumptions for full calibration for Human sensing targets as follows:

Parameters	Indoor Values	Outdoor Values
(u, std) for XPR of target	(19.81, 4.25) dB~~FFS~~	(19.81, 4.25) dB~~FFS~~

Agreement

The following introductory text is added before each of the ISAC deployment scenarios;

1. ISAC-UAV

In the ISAC-UAV scenario, the sensing targets are outdoor UAVs below or above the buildings in urban or rural areas. Monostatic or bistatic sensing can be performed using TRPs and/or UEs, including UEs on other UAVs.

2. ISAC-Automotive

In the ISAC-Automotive scenario, the sensing targets are passenger vehicles or trucks and buses traveling on roads and streets in urban and rural areas. Monostatic or bistatic sensing can be performed using TRPs and/or UEs, including UEs on other vehicles and roadside UEs (RSU-type UEs).

3. ISAC-Human

In the ISAC-Human scenario, the sensing targets are children and adult persons in indoor (room, office, factory) and outdoor (urban, rural) locations. Monostatic or bistatic sensing can be performed using TRPs and/or UEs in the corresponding communication scenarios.

4. ISAC-AGV

In the ISAC-AGV scenario, the sensing targets are automated guided vehicles (AGVs) inside a factory. Monostatic or bistatic sensing can be performed using TRPs and/or UEs in the corresponding communication scenario.

5. ISAC-Objects creating hazards

In the ISAC-Objects creating hazards scenario, the sensing targets are adult humans and children and animals in communication scenarios involving vehicles or high-speed trains. Monostatic or bistatic sensing can be performed using TRPs and/or UEs, including UEs on other vehicles and roadside UEs (RSU-type UEs).

Agreement

Updates to 7.9.7.1-4: Simulation assumptions for large scale calibration for AGV sensing targets as follows:

Parameters

Values

Component A of the RCS for each scattering point

-4.25 dBsm~~-1.37 dBsm~~

Note: based on AGV option 1~~For calibration purposes, other value(s) are not precluded.~~

Agreement

Updates to 7.9.7.2-4: Simulation assumptions for full calibration for AGV sensing targets as follows:

Parameters	Values
(u, std) for XPR of target	(9.60, 6.85) dB~~FFS~~

R1-2504364 FL Summary #2 on ISAC Scenarios and Calibrations Moderator (AT&T)

Agreement

Resolve square brackets for Table 7.9.1-4: Evaluation parameters for Automated Guided Vehicles sensing scenarios:

Sensing Target

3D mobility

Horizontal velocity with random straight-line trajectory

- Option 1: Uniform distribution in the range of up to 30 km/h

- Option 2: Fixed velocities [{3, 10] } km/h

R1-2504365 FL Summary #3 on ISAC Scenarios and Calibrations Moderator (AT&T)

R1-2504366 FL Summary #4 on ISAC Scenarios and Calibrations Moderator (AT&T)

9.7.22 ISAC channel modelling

R1-2503248 Channel modelling for ISAC Huawei, HiSilicon

R1-2503373 Views on Rel-19 ISAC channel modelling vivo, BUPT

R1-2503446 Discussion on ISAC channel modeling EURECOM

R1-2503525 Discussion on ISAC channel modeling Spreadtrum, UNISOC

R1-2503577 Discussion on ISAC channel modelling Samsung

R1-2503646 Discussion on ISAC channel modelling Pengcheng Laboratory

R1-2503698 Discussion on channel modelling for ISAC ZTE Corporation, Sanechips, CAICT

R1-2503720 Discussion on ISAC channel modelling Tejas Network Limited

R1-2503726 Discussion on ISAC channel modelling TOYOTA InfoTechnology Center

R1-2503753 Discussion on ISAC channel modeling InterDigital, Inc.

R1-2503761 Discussion on ISAC Channel Modeling SK Telecom

R1-2503804 Discussion on ISAC channel modelling CATT, CICTCI

R1-2503842 Discussion on ISAC channel modeling CMCC

R1-2503859 ISAC Channel Modeling and Measurement Validation BUPT, CMCC, VIVO, X-Net

R1-2503893 Discussion on ISAC channel model Xiaomi, BJTU, BUPT

R1-2503955 Discussion on ISAC channel modeling Nokia, Nokia Shanghai Bell

R1-2503969 Discussion on ISAC Channel Modeling Tiami Networks

R1-2503991 Channel modelling for integrated sensing and communication with NR NVIDIA

R1-2504013 Discussion on ISAC Channel Modeling NIST

R1-2504054 Discussion on ISAC channel modelling China Telecom

R1-2504069 Remaining issues on ISAC Channel Modeling Sony

R1-2504110 Discussion on ISAC Channel Modelling Panasonic

R1-2504119 Discussion on channel modelling for ISAC CALTTA

R1-2504159 Discussion on ISAC channel modelling Pengcheng Laboratory

R1-2504221 Study on ISAC channel modelling OPPO

R1-2504240 Discussion on Channel Modelling for ISAC Lenovo

R1-2504269 Discussion on ISAC channel modelling MediaTek Inc.

R1-2504337 Discussion on ISAC channel modelling Apple

R1-2504405 Discussion on ISAC channel modelling Qualcomm Incorporated

R1-2504455 Discussion on ISAC Channel Modelling Ericsson

R1-2504511 Discussion on ISAC Channel Modelling NTT DOCOMO, INC.

R1-2504567 Discussion on ISAC channel modelling LG Electronics

R1-2504161 Summary #1 on ISAC channel modelling Moderator (Xiaomi)

R1-2504162 Summary #2 on ISAC channel modelling Moderator (Xiaomi)

Agreement

Confirm the following working assumption with updates in red.

Working assumption

For vehicle with single/multiple scattering points, the bistatic RCS is generated by

• The values/pattern of A*B1 of bistatic RCS is given by:

where

- is applied to the within 0~180 degrees. k1= 6 and k2=1.65. is the bistatic angle between the incident ray and scattering ray within the plane of incident direction () and scattering direction ().

- The angles of () are the projections of the bisector angle on the vertical plane and the horizontal plane, respectively.

o ~~FFS:~~ ~~RCS value when~~ ~~is 180 degrees~~

- The effect of forward scattering is -Inf in Rel-19

- 5 sets of parameters Applicable Range of and Applicable Range of are applicable as defined for the monostatic RCS of vehicle with single/multiple SPSTs

- ~~Continue study on a new formula for~~ ~~to resolve the issue of angular discontinuity.~~

o ~~The new formula should retain following property: the linear bistatic RCS for a vehicle with single scattering point is the sum of the bistatic RCS of the multiple scattering points of the vehicle~~

o ~~the following formula can be a reference for the study~~

Agreement

The agreement on bistatic RCS for vehicle is reused for large size UAV and AGV.

- For large size UAV, k₁=6.05 and k₂=1.33

- For AGV, k₁=12 and k₂=1.45

Agreement

AGV can be modelled with multiple scattering points.

Ÿ The values/pattern of component A*B1 are generated by the following parameters

	in [°]	in [°]	in [°]	in [°]			*Range of* in [°]	*Range of* in [°]
Front	0°	13.68°	90°	13.68°	13.00	30.26	[0,180]	[0,360]
Left	90°	15.53°	75°	20.03°	7.27	24.53	[0,180]	[0,360]
Back	180°	12.49°	90°	11.89°	10.98	28.24	[0,180]	[0,360]
Right	270°	15.53°	75°	20.03°	7.27	24.53	[0,180]	[0,360]
Roof	/	/	0°	11.44°	11.77	29.03	[0,180]	[0,360]

- Note: For the scattering point associated with roof of the AGV, .

- Note: the measurements from companies are done by AGV option 1.

Agreement

Ÿ The bistatic RCS of UAV with small size is modelled as

- The values/pattern of A*B1 is given by

o Component A, i.e., : same as component A of mono-static RCS for UAV of small size

o dB, where is the bi-static angle between incident ray and scattered ray, is within 0 and 180 degree

o The effect of forward scattering is -Inf in Rel-19

- Component B2: same as component B2 of mono-static RCS for UAV of small size

Ÿ The bistatic RCS of Human with RCS model 1 is modelled as

- The values/pattern of A*B1 is given by

o Component A, i.e., : same as component A of mono-static RCS for Human with RCS model 1

o dB, where is the bi-static angle between incident ray and scattered ray, is within 0 and 180 degree

o The effect of forward scattering is -Inf in Rel-19

- Component B2: same as component B2 of mono-static RCS for Human with RCS model 1

Agreement

On the monostatic RCS of human with RCS model 2,

Ÿ The values/pattern of component A*B1 are generated by the following parameters

	in [°]	in [°]	in [°]	in [°]			Range of in [°]	Range of in [°]
Front	0	216.65	90	55.7	2.14	7.7	[0,180]	[-90, 90]
Back	180	216.65	90	55.7	2.14	7.7	[0,180]	[90,270]

Ÿ The standard deviation of component B2 is 3.94 dB

Agreement

The agreement on bistatic RCS for vehicle with single scattering point is reused to model bistatic RCS of human with RCS model 2

- k1=0.5714 and k2=0.1

Agreement

The following values of the RCS component A are applied to both monostatic and bistatic RCS of the target.

- UAV with large size: -5.85 dBsm

- Human with RCS model 2: -1.37 dBsm

o Note: measurement is based on adult

- Vehicle: 11.25 dBsm

o Note: measurement is based on vehicle type 1 and 2

- AGV: -4.25 dBsm

o Note: measurement is based on AGV option 1

Note: component A on its own may not fully reflect the RCS in the target channel. This note will not be captured in the TR.

Agreement

The mean and standard deviation values of XPR of sensing target AGV for monostatic sensing and bistatic sensing are (9.60, 6.85) dB.

Conclusion

The component B2 of two different targets are generated independently.

Conclusion

The component XPR/initial random phase of two different targets are generated independently.

Agreement

In order to generate Tx-target link, target-Rx link and the background channel between a RSU-type UE and another node (TRP, pedestrian UE, vehicle UE, RSU-type UE), the following reference TRs are adopted

Case	Tx/Rx	Rx/Tx	Existing TRs as starting point
	TRP	RSU-type UE	Highway and Urban grid • B2R link in section 6 of TR 37.885
	RSU-type UE	normal UE	Highway and Urban grid • V2V link in section 6 of TR 37.885, with antenna height at RSU is 5m
	RSU-type UE	RSU-type UE	Highway and Urban grid • V2V link in section 6 of TR 37.885, with antenna height at RSU is 5m
	RSU-type UE	vehicle UE	Highway and Urban grid • V2V link in section 6 of TR 37.885, with antenna height at RSU is 5m

Agreement

The initial random phase (generated in Step 10, section 7.5, TR38.901) is the same for the same ray in Tx-target link and target-Rx link of a target for monostatic sensing.

Agreement

For UMi-AV and RMa-AV with aerial UE as sensing transmitter or receiver, the values of parameters to generate background channel for UT monostatic sensing are provided in the following table

Scenario	UT monostatic sensing
Scenario	UMi-AV	RMa-AV
Distribution of 2D distance between Tx and reference points


Distribution of height of reference points

Note 1: Distributions of height and distance of reference point are not subject to geographical constraints on TRP for the corresponding deployment scenario.

Note 2: The reference points for generating the UT monostatic background channel have the same velocity as UT.

Note 3: In the UT monostatic sensing in UMa and UMi scenario, the ZOD offset in the background channel should be set as 0

Agreement

To generate the background channel for TRP monostatic sensing and UT monostatic sensing, ‘ +’ is used to model the absolute delay between the Tx and each reference point.

Agreement

Power threshold for path dropping after concatenation is up to -40dB for target channel for option 3. Up to company to choose a value in the implementation.

Power threshold for path dropping after concatenation is up to -25dB for target channel for option 0. Up to company to choose a value in the implementation.

For calibrations for both option 0 and option 3, power threshold for path dropping after concatenation is -40dB for target channel.

Agreement

To generate the absolute delay model for sensing scenarios Urban grid, highway and HST, for both target channel and background channel

• For Urban grid, the values of parameters for of scenarios UMa are reused.

• For Highway, the values of parameters for of scenarios RMa and UMa are reused for FR1 and FR2 respectively.

• For HST, the values of parameters for of scenarios RMa and UMa are reused for FR1 and FR2 respectively.

Note: no measurements on of the 3 scenarios are submitted in Rel-19.

Agreement

Spatial consistency is not modelled for

Ÿ the links that are generated referring to channel models with parameter values of different communication scenarios

- E.g., between TRP-target/UT link in one scenario and target/UT-UT link in another scenario

Ÿ the background channels for TRP monostatic sensing of different TRPs

Agreement

Spatial consistency is not modelled between TRP-target/UT link and target/UT-UT link for sensing scenario UMi, InH and InF.

Agreement

Spatial consistency is not modelled between TRP-TRP link and any other links for ISAC channel.

Agreement

Spatial consistency can be enabled for multiple scattering points of a target.

Spatial consistency, if enabled, for the links between BS/UT and multiple scattering points of a target are modelled as if multiple scattering points are multiple targets.

Agreement

The existing horizontal correlation distance in Table 7.6.3.1-2 in TR38.901 is used as the correlation distance for 3D spatial consistency for ISAC channel at least for UAV scenario, within same ‘Applicability range in terms of aerial UE height (defined in 36.777)’.

Agreement

EO type-2 can be modelled in NLOS condition.

Agreement

In sensing scenario UMi, UMa, if the height of a scattering point of target is less than 1.5m, for pathloss calculation,

- use h_UT 1.5 m for breakpoint distance (d_BP) calculation

- Note: h_UT 1.5 m is only used for d_BP calculation. The exact h_UT of the scattering point is still used to determine all other parameters of ISAC channel, e.g., delay, AOD/ZOD/AOA/ZOA, etc.

Agreement

On background channel modelling,

• Spatial consistency is not supported for TRP monostatic sensing across different TRPs

• Spatial consistency is not supported for UE monostatic sensing across different UEs

• Spatial consistency is not supported across different Reference Points for same TRP for TRP monostatic sensing

• Spatial consistency is not supported across different Reference Points for same UE for UE monostatic sensing

Agreement

• RCS component B2 of different direct/indirect paths of a target in the target channel are generated independently.

• On the RCS component B2 of a direct/indirect path of a target in the target channel, the same value of B2 applies to a path before the value of B2 is updated.

- Note: whether/how/when to update B2 can be discussed in evaluation phase or up to companies’ choices

Agreement

• XPR of different direct/indirect paths of a target in the target channel are generated independently.

• On the XPR of a direct/indirect path of a target in the target channel, the same value of XPR applies to a path before the value of XPR is updated.

- Note: whether/how/when to update XPR can be discussed in evaluation phase or up to companies’ choices

Agreement

• Initial random phase of different direct/indirect paths of a target in the target channel are generated independently.

• On the initial random phase of a direct/indirect path of a target in the target channel, the same value of initial random phase applies to a path before the value of initial random phase is updated.

- Note: whether/how/when to update initial random phase can be discussed in evaluation phase or up to companies’ choices

R1-2504163 Summary #3 on ISAC channel modelling Moderator (Xiaomi)

Agreement

The follow TP is used generate the power (except for the impact of polarization matrix of EO type-2) of the ray specular reflected by an EO type 2 in the STX-SPST link or SPST-SRX link.

7.9.5.2 Type-2 environment object

< Unchanged text omitted >

5. In Step 10 in Clause 7.9.4.1,

for a NLOS ray specularly reflected by a type-2 EO, if present, in the SPST-SRX link and the STX-SPST link is determined as follows.

- If the STX-SPST link is in LOS condition,

- If the STX-SPST link is not in LOS condition, , where is the pathloss of STX-SPST link assuming LOS condition.

- If the SPST-SRX link is in LOS condition,

- If the SPST-SRX link is not in LOS condition, , where is the pathloss of SPST-SRX link assuming LOS condition.

< Unchanged text omitted >

Agreement

To generate the absolute delay model for sensing scenarios UMi-AV, UMa-AV and RMa-AV, for both target channel and background channel,

• For the TRP-TRP link and TRP- terrestrial UE link, the values of parameters for of scenarios UMi, UMa and RMa are respectively reused.

• For the terrestrial UE- terrestrial UE link, the values of parameters for of scenarios UMi are reused.

• For the TRP- aerial UE link, the values of parameters for of scenarios UMi, UMa and RMa are respectively reused.

• For the terrestrial UE- aerial UE link, the values of parameters for of scenarios UMi are reused.

• For the aerial UE- aerial UE link, the values of parameters for of scenarios UMi are reused.

Note: no measurements on of the scenarios UMi-AV, UMa-AV and RMa-AV are submitted in Rel-19.

Agreement

• Remove the brackets for first sub-bullet under Step 4 for Clause 7.9.4.2 in the CR to TR 38.901.

• On the absolute delay of the background channel for both TRP and UE monostatic sensing, three are independently generated and respectively applied to the 3 channels between the STX/SRX and the 3 RPs.

Agreement

To generate the channel between an aerial UE and a normal UE,

Ÿ The LOS probability is generated by:

Low-UAV

Mid-UAV

High-UAV

UMi in Table 7.4.2-1 in TR 38.901 for UMi-AV/UMa-AV/RMa-AV

UMi-AV in Table B-1 in TR 36.777 for BS to mid UAV region for UMi-AV/UMa-AV/[RMa-AV]

~~RMa-AV in Table B-1 in TR 36.777 for BS to mid UAV region~~

UMi-AV in Table B-1 in TR 36.777 for BS to [high] UAV region for UMi-AV/UMa-AV/[RMa-AV]

~~RMa-AV in Table B-1 in TR 36.777 for BS to mid UAV region~~

Ÿ The pathloss and shadow fading are generated using TRP-aerial UE link of UMi-AV in Annex A and B of TR 36.777 by setting h_BS =1.5m for FR1

Note:

Ÿ The height ranges of low-UAV, Mid-UAV and High-UAV are defined following the applicability range in terms of aerial UE height in Table B-1: LOS probability in TR 36.777

Ÿ The second height range for UMi-AV is further divided into 2 regions, i.e., [22.5, 100] and [100, 300] for mid-UAV and high-UAV, respectively.

Conclusion

No further study on power normalization of target channel and background channel of ISAC channel in Rel-19

- Note: sub-section “7.9.5.3 Power normalization across target channel and background channel” in the TR remains as a placeholder with the following text.

o To combine the target channel and the background channel, power normalization can be applied to keep the same/similar channel power as the background channel without sensing target.

Agreement

The polarization matrix of a direct/indirect path i of a scattering point of a target is defined in LCS.

Agreement

To generate the channel between a first aerial UE with height h1 and a second aerial UE with height h2, abs(h1-hBS) <= abs(h2-hBS),

Ÿ The LOS probability between the two aerial UEs is generated by:

	Low-UAV	Mid-UAV	High-UAV
Low-UAV	UMi in Table 7.4.2-1 in TR 38.901 for UMi-AV/UMa-AV/RMa-AV	UMi-AV in Table B-1 in TR 36.777 for BS to mid UAV region for UMi-AV/UMa-AV/[RMa-AV] ~~RMa-AV in Table B-1 in TR 36.777 for BS to mid UAV region~~	UMi-AV in Table B-1 in TR 36.777 for BS to [high] UAV region for UMi-AV/UMa-AV/[RMa-AV] ~~RMa-AV in Table B-1 in TR 36.777 for BS to mid UAV region~~
Mid-UAV	UMi-AV in Table B-1 in TR 36.777 for BS to mid UAV region for UMi-AV/UMa-AV/[RMa-AV] ~~RMa-AV in Table B-1 in TR 36.777 for BS to mid UAV region~~	UMa-AV in Table B-1 in TR 36.777 for BS to mid UAV region for UMi-AV/UMa-AV RMa-AV in Table B-1 in TR 36.777 for BS to mid UAV region	1
High-UAV	UMi-AV in Table B-1 in TR 36.777 for BS to [high] UAV region for UMi-AV/UMa-AV/[RMa-AV] ~~RMa-AV in Table B-1 in TR 36.777 for BS to mid UAV region~~	1	1

Ÿ The pathloss and shadow fading between two aerial UEs are generated using TRP-aerial UE link of UMi-AV in Annex A and B of TR 36.777 by setting height of TRP equal to the height of the first aerial UE.

Note:

Ÿ The height ranges of low-UAV, Mid-UAV and High-UAV are defined following the applicability range in terms of aerial UE height in Table B-1: LOS probability in TR 36.777

Ÿ The second height range for UMi-AV is further divided into 2 regions, i.e., [22.5, 100] and [100, 300] for mid-UAV and high-UAV, respectively.

R1-2504164 Summary #4 on ISAC channel modelling Moderator (Xiaomi)

Agreement

Update the agreements on LOS probability calculation for channel between an aerial UE and a normal UE as follows.

Low-UAV

Mid-UAV

High-UAV

UMi in Table 7.4.2-1 in TR 38.901 for UMi-AV/UMa-AV/RMa-AV

UMi-AV in Table B-1 in TR 36.777 for BS to mid UAV region for UMi-AV/UMa-AV~~/[RMa-AV]~~

RMa-AV in Table B-1 in TR 36.777 for BS to mid UAV region for RMa-AV

UMi-AV in Table B-1 in TR 36.777 for BS to high UAV region for UMi-AV/UMa-AV~~/[RMa-AV]~~

RMa-AV in Table B-1 in TR 36.777 for BS to high UAV region for RMa-AV

Agreement

Update the agreements on LOS probability calculation for channel between two aerial UE as follows.

	Low-UAV	Mid-UAV	High-UAV
Low-UAV	UMi in Table 7.4.2-1 in TR 38.901 for UMi-AV/UMa-AV/RMa-AV	UMi-AV in Table B-1 in TR 36.777 for BS to mid UAV region for UMi-AV/UMa-AV~~/[RMa-AV]~~ RMa-AV in Table B-1 in TR 36.777 for BS to mid UAV region for RMa-AV	UMi-AV in Table B-1 in TR 36.777 for BS to high UAV region for UMi-AV/UMa-AV~~/[RMa-AV]~~ RMa-AV in Table B-1 in TR 36.777 for BS to high UAV region for RMa-AV
Mid-UAV	UMi-AV in Table B-1 in TR 36.777 for BS to mid UAV region for UMi-AV/UMa-AV~~/[RMa-AV]~~ RMa-AV in Table B-1 in TR 36.777 for BS to mid UAV region for RMa-AV	UMa-AV in Table B-1 in TR 36.777 for BS to mid UAV region for UMi-AV/UMa-AV RMa-AV in Table B-1 in TR 36.777 for BS to mid UAV region	1
High-UAV	UMi-AV in Table B-1 in TR 36.777 for BS to high UAV region for UMi-AV/UMa-AV~~/[RMa-AV]~~ RMa-AV in Table B-1 in TR 36.777 for BS to high UAV region for RMa-AV	1	1

Agreement

To determine the LOS condition of any link in ISAC channel model, when EO type-2 is modelled, the following two options are agreed as solutions:

• Option A: If type-2 EO is in the LOS ray of the link, the LOS probability is p, p=0, and otherwise use the LOS probability equation defined in existing TRs to determine the LOS/NLOS condition

• Option C: Use the LOS probability equation to determine the LOS/NLOS condition of the link.

Note1: in which conditions/scenarios to use option A or option C can be determined in future evaluations.

Note2: as already agreed, monostatic background channel is always NLOS

Agreement

EO type-2 can be optionally modelled in background channel when EO type-2 is modelled in target channel.

Conclusion

Other than RCS for human, vehicle, AGV, UAV, no other RCS for other objects is introduced in Rel-19.

l Future studies are not precluded for adding RCS of other objects/sizes for modelling target or EO type-1, based on validation results from companies.

R1-2504165 Summary #5 on ISAC channel modelling Moderator (Xiaomi)

Conclusion

Delete subsection 7.9.6 from the draft CR. For ISAC, no enhancement to existing TR38.901 LLS channel model is introduced in Rel-19.

Agreement

• The existing blockage model A/B procedures can be reused to model the blocking effect due to a target as an optional feature

- Applicable to the LOS/NLOS rays in the background channel of the target

- Applicable to the LOS/NLOS rays in the Tx-target and target-Rx link of another target

• The location, orientation and size of the target as a blocker is known before applying the blockage model A/B.

Agreement

• The square brackets on formula 7.9.5-10 (copied below) in the draft CR are removed

The effective polarization matrix of the type-2 EO reflection path is given by

[ (7.9.5-10)]

• Encourage companies to check and compare with the results that can be obtained with Alt2 and Alt3 below. If problem is found, RAN1 will revise TR 38.901 by new CR.

Alt2

[ (7.9.5-10)]

With reusing the legacy transformation method for deriving and .

Alt3

[ (7.9.5-10)]

Where,

- . represents the normal vector of the incident plane. , in which and . represents the spherical basis vector of incident ray in vertical direction. represents the spherical basis vector of incident ray in horizontal direction. .

- . represents the polar basis vector of scattering ray in vertical direction. represents the polar basis vector of scattering ray in horizontal direction. . .

Conclusion

There is no consensus to introduce an exact formula for micro-Doppler in Rel-19. The placeholder in the channel impulse response is kept in the draft CR.